4 ms·
But that's not what Linode did. Linode put the private key right next to the public key, where anyone who compromised their web frontend could get at it. If th
by jmillikin 13y ago
But that's not what Linode did. Linode put the private key right next to the public key, where anyone who compromised their web frontend could get at it.
If they had kept their private key where it belonged, we wouldn't be having this discussion because their security alert would have said "...and we have verified that no credit card data was accessed".
- dllthomas 13y agoAnd the problem was the private key being on the server running the web front-end, and that's what should be criticized. Presence of a public key does not a webserver make.