Tls self_signed - path to ssl certs?

eva2000 · August 6, 2016, 5:19am

With tls self_signed option where are the paths to the ssl cert files ?

As part of my Caddy integration, I also plan to be able to list all ssl certs and their expiry dates so that I can setup push notifications to mobile/tablet devices. But can’t find where these self signed ssl certs are located ?

elcore · August 6, 2016, 9:14am

The self-signed certs are kept in memory only; they’re not written to disk.

github.com/caddyserver/caddy

Self Signed certificates not in memory?

opened 12:17AM - 20 Jul 16 UTC

closed 11:01PM - 21 Jul 16 UTC

kilpatty

feature

Is there anyway to have Caddy generate a self signed certificate and store it in… the normal area? ~/.caddy. This would really help as we could make the certificates persistent throughout different machines and builds. What I mean by this is that if I use Caddy inside of a docker container, every time I restart that container a new self signed certificate is generated, thus I have to add that new certificate to be trusted by my local browser. Instead, if we were able to persist certificates in the same way that real certs are persisted, then we would only need to trust one self signed cert, and all members of a development team could also just trust that same cert. Sorry for the wall of text! If there is someway I could help with this I can definitely try. Let me know what you think! :)

eva2000 · August 6, 2016, 3:22pm

cheers @elcore looks like will just need to get that info via openssl insead

echo | openssl s_client -connect google.com:443 2>/dev/null | openssl x509 -noout -dates
notBefore=Jul 28 11:48:19 2016 GMT
notAfter=Oct 20 11:40:00 2016 GMT

system · November 4, 2016, 3:22pm

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.