4 ms·
Whoa, interesting. Does this differ from LetsEncrypt?
by lessclue 9y ago
Whoa, interesting. Does this differ from LetsEncrypt?
- deleted 9y ago[deleted]
- petee 9y agoIts backed by Comodo :D I certainly don't like the complete lack of information on the webpage though...
- bigiain 9y agoThe 12 month validity - which means it's way more useful if you want to pin certificates in a mobile app...
- sandGorgon 9y agothis is huge. And a killer difference. This means you can bake these certificates into Docker images as well.
- f2n 9y agoPSA: Don't do this. Secrets don't belong in docker images, they belong in proper secret management tools.
- sandGorgon 9y agoI get what you mean - i would say that not everyone has a devops team and is setting up a whole bunch of infrastructure. I would rather recommend a ssl certificate baked into a docker image (stored in a private registry) versus no https at all even if you use a secrets management tool, there are very few (probably none) that can bootstrap a Letsencrypt api. So this new one makes that possible as well.
- icebraining 9y agoIf you want something simple, how about just installing nginx on the host to forward-proxy your Docker container?
- sandGorgon 9y agobut how is that more secure or simpler than running a docker image ? to setup the nginx on my host, i would still have to store the certificates somewhere right. Docker is not what is making this thing complicated.
- icebraining 9y agoUsing nginx and a let's encrypt client on the host, the certificates are only generated and kept inside the machine itself. That's safer than baking them into the Docker image, which will be copied around.
- jsiepkes 9y agoHow so? You pin the public key part in the cert not the whole cert itself. The key you use (should) stay the same.