For localhost, you typically just generate a self-signed certificate
Ah, yes, that [mythical] developer which entire company depends on and he has one self-signed certificate to fulfill all the needs.
Everyone else has many developers running many local and not-local development (and not only development) environments which can have a full access to Internet or be isolated.
doesn't need to be trusted by everyone, as the dev can just add it to their local store
And this is how the certificate warnings starts to be dismissed without reading and this is how the local self-signed certs find a ways to the local stores of the every computer device in the company.
Yes indeed. Those who think pki is easy only understand that generating certs is easy, and don’t realize that managing trust of your certs is the difficult part. If you are willing to do a bunch of self-signed certs that aren’t trusted by all the right parties, you’re missing half the point of pki.
Comments
Ah, yes, that [mythical] developer which entire company depends on and he has one self-signed certificate to fulfill all the needs.
Everyone else has many developers running many local and not-local development (and not only development) environments which can have a full access to Internet or be isolated.
And this is how the certificate warnings starts to be dismissed without reading and this is how the local self-signed certs find a ways to the local stores of the every computer device in the company.
Yes indeed. Those who think pki is easy only understand that generating certs is easy, and don’t realize that managing trust of your certs is the difficult part. If you are willing to do a bunch of self-signed certs that aren’t trusted by all the right parties, you’re missing half the point of pki.