-
Notifications
You must be signed in to change notification settings - Fork 61
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
Option to setup preferred-chain #73
Comments
I believe this might be what you're looking for: https://github.com/do-know/Crypt-LE#alternative-certificates-support But let me know if it's not. |
That 's not what I meant. I'm not sure if it's by design but Crypt::LE enforces an alternative LE chain. It means that (currently expired) DST root cert is not used in Crypt::LE generated certs `
LE cert with DST
currently that is a good thing because DST root has expired on 30th of September, But just for the record
So an option is required to use DST -> ISRG -> Client authority chain (which is default for certbot) Please don't change the current default (ISRG Self Signed -> ISRG -> Client) In short: certbot defaults to : DST -> ISRG -> Client chain when requesting cert from LE and requires an option Crypt::LE defaults to ISRG Self Signed ->ISRG -> Client (an alternative chain) and requires an option to go with DST -> ISRG -> Client Both chains has pros and cons, but JFTR Crypt::LE defaults to the option that turn of a majority of old android devices so may be an option is required to go with DST... |
Is there any option to setup preferred chain?
like
./certbot certonly --apache -d ${DOMAIN} --dry-run --preferred-chain="ISRG Root X1"
with DST Root CA X3 now expired ?
The text was updated successfully, but these errors were encountered: