Dehydrated doesn't have hardcoded chains. It uses the chain as provided by the CA. You can even select alternate chains the CA is offering using the PREFERRED_CHAIN config value or the --preferred-chain CLI option.
@lukas2511 commented on GitHub (Oct 2, 2021):
Dehydrated doesn't have hardcoded chains. It uses the chain as provided by the CA. You can even select alternate chains the CA is offering using the `PREFERRED_CHAIN` config value or the `--preferred-chain` CLI option.
While you're right, Lukas, this probably should be put on the top of readme (both github and else) since it does bite almost everyone providing external certs. The full compatible chain (with expired signed X1) fails on any embedded crap (like TVs) as well as many clients using openssl 1.0.xx.
As a community service, instead of letting them find it in closed issues. :-)
@grinapo commented on GitHub (Oct 3, 2021):
While you're right, Lukas, this probably should be put on the top of readme (both github and else) since it **does bite almost everyone** providing external certs. The full compatible chain (with expired signed X1) fails on any embedded crap (like TVs) as well as _many_ clients using openssl 1.0.xx.
As a community service, instead of letting them find it in closed issues. :-)
Also, solution is spelled out in #842 .
Dehydrated doesn't have hardcoded chains. It uses the chain as provided by the CA. You can even select alternate chains the CA is offering using the PREFERRED_CHAIN config value or the --preferred-chain CLI option.
Thanks , readme is not very clear with this
@whizzygeeks commented on GitHub (Nov 19, 2021):
>
>
> Dehydrated doesn't have hardcoded chains. It uses the chain as provided by the CA. You can even select alternate chains the CA is offering using the `PREFERRED_CHAIN` config value or the `--preferred-chain` CLI option.
Thanks , readme is not very clear with this
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @whizzygeeks on GitHub (Oct 2, 2021).
Update root chain with new ones specified in https://letsencrypt.org/certificates/
@lukas2511 commented on GitHub (Oct 2, 2021):
Dehydrated doesn't have hardcoded chains. It uses the chain as provided by the CA. You can even select alternate chains the CA is offering using the
PREFERRED_CHAINconfig value or the--preferred-chainCLI option.@grinapo commented on GitHub (Oct 3, 2021):
While you're right, Lukas, this probably should be put on the top of readme (both github and else) since it does bite almost everyone providing external certs. The full compatible chain (with expired signed X1) fails on any embedded crap (like TVs) as well as many clients using openssl 1.0.xx.
As a community service, instead of letting them find it in closed issues. :-)
Also, solution is spelled out in #842 .
@whizzygeeks commented on GitHub (Nov 19, 2021):
Thanks , readme is not very clear with this