search for: wildcard_crt

...variants running with identical configs and certs (the only differences are due to config syntax changes in dovecot 2.3), so for example on both I have: ssl_ca = </etc/openssl/certs/wildcard_ca.pem (this file contains single intermediate certificate of my CA) ssl_cert = </etc/openssl/certs/wildcard_crt.pem (this contains single cerificate for my *.example.com domain) ssl_key = # hidden, use -P to show it (and one key) No alt certs in use. Chain is: - CA trusted by clients (this certificate isn't provided by my dovecot, it's not needed) - wildcard_ca.pem - intermediate CA - wildcard_cr...

...> </div> <div> ssl_ca = </etc/openssl/certs/wildcard_ca.pem </div> <div> (this file contains single intermediate certificate of my CA) </div> <div> <br> </div> <div> ssl_cert = </etc/openssl/certs/wildcard_crt.pem </div> <div> (this contains single cerificate for my *.example.com domain) </div> <div> <br> </div> <div> ssl_key = # hidden, use -P to show it </div> <div> (and one key) </div> <div>...

...the only differences are due to config syntax changes in dovecot 2.3), >> so for example on both I have: >> >> ssl_ca = </etc/openssl/certs/wildcard_ca.pem >> (this file contains single intermediate certificate of my CA) >> >> ssl_cert = </etc/openssl/certs/wildcard_crt.pem >> (this contains single cerificate for my *.example.com domain) [dovecot 2.3+ does not provide intermediate CA cert to clients any more] >> 2.3.x announcements and upgrade wiki mention no such behaviour change, >> so I assume it is a regression. >> >> Now doing...