Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Full certificate chain in export #24

Closed
Ich79 opened this issue May 18, 2018 · 10 comments
Closed

Full certificate chain in export #24

Ich79 opened this issue May 18, 2018 · 10 comments

Comments

@Ich79
Copy link

Ich79 commented May 18, 2018

Hey!
I am using autoACME and we're very happy with it for IIS. We also have a mailserver (hMailserver to be precise) and I would also like to use the let's encrypt certificate for that.
Unfortunately the certificate is missing the full chain which makes it much harder to use the certificates on for other services.
Maybe it's enough to make AcmeContext.cs:98 configurable. In the end hMailserver requires the certificate as a textfile, not PFX but maybe it works.

Is this something which you might consider? Like a parameter e.g. fullchain=true?

Even if not, thanks a lot for this piece of software!
Best regards,
Boris

@Ich79
Copy link
Author

Ich79 commented May 19, 2018

Just to be sure: I mean full chain in the PEM file, not PFX ;)

@ridercz
Copy link
Owner

ridercz commented May 19, 2018

First of all: Why would hMailServer need full chain? I use it as well, without full chain and without any problems. LE certificates have correct Authority Info Access, so client can build their chain without any problems.

Second, I can probably add it in future version, why not.

@Ich79
Copy link
Author

Ich79 commented May 21, 2018

Hi!
Oh ok, I tried it once with the certificate provided by autoACME and had issues with https://www.checktls.com/ as the full chain was not provided by the server.
Maybe it messed something up. If so, sorry for the issue opened!
Thanks!
Boris

@eleasarchriso
Copy link

@ridercz - can you please provide the steps you take for using the certificates in hmailserver? With win-acme I got a chain/key pem file that I was able to use.

@avonwyss
Copy link
Collaborator

@eleasarchriso AutoACME generates PFX files, You can use OpenSSL on the command line (and thus also script that) to split these up into their parts (e.g. PEM and PVK files), see for instance https://support.comodo.com/index.php?/comodo/Knowledgebase/Article/View/548/7/

@eleasarchriso
Copy link

Ok thanks. Yes this is what I am doing now. I thought there might be some setting/option in AutoAcme that I was missing like the PEM folder in the configs.
Is there any option to run some script after a new certificate was downloaded where I could plug in this generation of the hmailserver certificates?

@avonwyss
Copy link
Collaborator

@eleasarchriso No, I'm not aware of such a feature, but you could open a request for that: Pre- and post-request scripts could maybe be added to the certificate host information, so that only specific certificates would trigger these actions.

@Ich79
Copy link
Author

Ich79 commented Feb 22, 2019

Hi!
I was just playing around with it. Most software (e.g. Joomla, MX Toolbox, luxsci) apparently will not consider the certificate trustworthy, if the server is not sending the full chain. Currently hMailserver is using the PEM and CRT file, that are created during issuing process (completely ignoring the PFX file) as is.

Any plans on exporting the full chain into the CRT file? That might fix this issue. It does work, if I copy the contents manually into the file..

Thanks,
Boris

@avonwyss
Copy link
Collaborator

@Ich79 I assume that when you say "the full chain" you mean the chain up to (but excluding) the root CA, right? E.g. the domain cert and the intermediate cert, but not the root cert.

avonwyss added a commit to avonwyss/AutoACME that referenced this issue Feb 22, 2019
ridercz added a commit that referenced this issue Feb 23, 2019
Implements #24 - add chain certificates to CRT file
@ridercz
Copy link
Owner

ridercz commented Feb 23, 2019

Added in 1.6.1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants