3 ms·
> This is the certificate used to verify the identity of the cloud server. The file contains the “VeriSign Class 3 Public Primary Certification Authority – G5”
by lultimouomo 6y ago
> This is the certificate used to verify the identity of the cloud server. The file contains the “VeriSign Class 3 Public Primary Certification Authority – G5” root certificate. This means the only check performed when establishing a TLS connection to the cloud is if the provided server certificate has been signed by the Symantec/VeriSign CA for Extended Validation (EV) certificates (CA pinning). A determined attacker could buy his own EV certificate and use it to impersonate a cloud server.
This part I don't get. Do they mean the firmware verifies the CA but NOT that the cert is actually for the domain/CN they want? If they made such a glaring mistake I would expect the write up to say it explicitly.
The way this is written seems to imply that all you need to impersonate a server is to buy a cert from the same CA it uses, which is obviously not the case.
- bluesign 6y agoYou missed the part where you can change the server address with remote command. Basically you can change cloud server address, but it will still check for symantec root, so you need to buy EV certificate from them.
- tinus_hn 6y agoWindows has a prominent setting that does exactly this for 802.1x authentication: choose the authority from a big, prominent list and optionally specify the server name it‘ll automatically send your credentials to (over wireless, no less). edit I’m not buying his argument that because the root certificate is on the image, that’s the only thing the script checks.