07-06-2015, 03:36 PM
(This post was last modified: 07-06-2015, 03:53 PM by Canis-Major.)
In my testing, on every site, there is talk of the 'private' whatever, so I think it would be good to have a central scource where the information is found, since it is not in fact a hack, but much sought after knowledge:
In snmp, we have public and private STRING.
In cert's, we have public and private KEY
By forcing an update we can see private key SCOURCE in console.
In downloaded config we see:
cmMIC and cmtsMIC which create when combined, the private (isp) string all seek. This is NOT the private string of snmp. But can allow it.
Is the cmMIC in config, the private KEY SCOURCE mentioned in console?
If so, then the cmtsMIC is the isp key SCOURCE?
So how can a modem verify the key we seek, or is it only cmts that can do?
In snmp, we have public and private STRING.
In cert's, we have public and private KEY
By forcing an update we can see private key SCOURCE in console.
In downloaded config we see:
cmMIC and cmtsMIC which create when combined, the private (isp) string all seek. This is NOT the private string of snmp. But can allow it.
Is the cmMIC in config, the private KEY SCOURCE mentioned in console?
If so, then the cmtsMIC is the isp key SCOURCE?
So how can a modem verify the key we seek, or is it only cmts that can do?