4 ms·
If it causes that much irritation, have you considered making your own CA, adding it to your browsers, and then using that to sign your temporary certificates?
by omh 16y ago
If it causes that much irritation, have you considered making your own CA, adding it to your browsers, and then using that to sign your temporary certificates?
It's quite straightforward to do this with openssl.
- Silhouette 16y agoI suppose that would be a possibility, but we'd still have to configure every browser on every machine to support that CA and then generate a certificate for every new project. I'd rather just be able to click once in my browser to accept the unsigned certificate, instead of jumping through tedious hoops that I don't believe really help anyone.
- acdha 16y agoSo rather than click once to install your internal CA you'd prefer to click once for every new site you add?
- Silhouette 16y agoYou're assuming it would be a single CA. That is, unfortunately, unlikely: we work on a variety of projects for various clients and in conjunction with various other contractors/development teams, and each project will have its own requirements for what needs to be signed and by whom. About the only thing they do have in common is that no-one goes out and spends lots of money on certs for every random development server they're using, they all self-sign in one form or another.
- kahawe 16y ago> If it causes that much irritation, have you considered making your own CA, adding it to your browsers, and then using that to sign your temporary certificates? A good fix but under the light of the looming issues describe in the link above: why invest all that time implementing and then defending this feature in the first place - for a negligible (at best) security benefit?