3 ms·
There's more to it than you've seen so far. Think about environments with hosts starting on demand. You need to encrypt data in flight -> how do you automatical
by viraptor 10y ago
There's more to it than you've seen so far. Think about environments with hosts starting on demand. You need to encrypt data in flight -> how do you automatically assign a new certificate to an instance on startup? You can't do it with an airgapped system.
- revelation 10y agoIf you're going to automatically create certificates you are shifting the entire authentication burden to that automated system. This is the exact issue with the public CA system, their automated processes have been found lacking and now what they certify can not be trusted.
- viraptor 10y agoThe topic was internal CAs. Those have completely different requirements and possibilities than public ones. The authentication will look completely different as well. You just can't compare those issues. And you're missing the point I raised as well - if you have hosts coming up automatically, you either need automatic certificates, or shared keys. As long as you rely on SSL, there's no other way to go. (For example of authentication: public CA verifies your domain, internal CA can ask the hypervisor to verify a token on your instance - not remotely in the same class)
- deleted 10y ago[deleted]