Closed killbus closed 3 years ago
Should be possible, however for now I don't know what might be the best way to implement this feature. Something that came up in my mind was to add a "switch" which toggle between appending both public and private key into a single file. This approach is okay until someone wishes a "mixed" mode, allowing users to selectively append a domain's public and private key to a single file. If we really need to implement a mixed mode, I hope that extending command argument parsing in Bash won't be a hassle. some stuffs like haproxy need certificate contains both the public certificate and private key, maybe we need a chain.pem like this? cat cert.pem key.pem > fullchain.pem — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.
PKCS#12 support would be good too.
PKCS#12 support would be good too.
This does require openssl
, doesn't it?
However, this is sort of out of scope in this issue. Maybe it's better to create a separate issue for PKCS#12 support.
Yes. I can't remember what I wanted this for but I'm sure others might find it useful.
Hi. I tried to create a pull request since I needed this feature for myself. For me it is working that way.
some stuffs like haproxy need certificate contains both the public certificate and private key, maybe we need a chain.pem like this?
cat cert.pem key.pem > domain.pem