|
|
|
|
|
|
by Sanddancer
3926 days ago
|
|
|
For one example, deploy servers and have them already verified, so a new box that you know you personally set up will not give a warning [1]. One of the most underutilized parts of SSL certificates is that you can verify who /you/ are, so any kind of server, including webservers, don't need passwords, because they already have the invite list [2]. This part is admittedly a lot crunchier than the first example because people haven't spent nearly enough time getting it working nicely. Basically, good use of certs can replace a lot of systems where you know what it is and they know what you are. [1] https://www.digitalocean.com/community/tutorials/how-to-crea... [2] http://nategood.com/client-side-certificate-authentication-i... |
|
|