3 ms·
For the cert part, LetsEncrypt specifically recommend against that: https://letsencrypt.org/docs/certificates-for-localhost/ https://letsencrypt.org/docs/certif
by stephenr 8y ago
For the cert part, LetsEncrypt specifically recommend against that: https://letsencrypt.org/docs/certificates-for-localhost/ https://letsencrypt.org/docs/certificates-for-localhost/
For the dns part, I honestly think a hosts file entry is more flexible, as you can support environments using vms/containers etc with a guest that has a dhcp address.
- sonaltr 8y agoThe security issue comes in when you ship the private key - if you are following best practices - won't the private key be different for each domain / managed in a better way?
- stephenr 8y agoSo, now you're going to give each member of your team a way to authorise valid certificates for your domain? Great, I don't want to imagine what your HR/security vetting process will be after the first abuse of that power.
- sonaltr 8y agoI had not thought about that...great points! This is way simpler in that case!