dovecot 2.2.25 BUG: local_name is not matching correctly
Bug report:
When using dovecot 2.2.25 SNI capability it doesn't always match proper vhost config. For example if we have such config:
local_name imap.example.com { ssl_cert = </etc/certs/cert.imap.example.com.pem ssl_key = </etc/certs/cert.imap.example.com.pem }
but imap client sends mixedcase SNI hostname like "IMAP.example.com" then dovecot won't match above local_name imap.example.coml config section.
IMO dovecot should do case insensitive comparison. Case sensitive matching for DNS names makes little sense.
-- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )
On 13.10.2016 16:09, Arkadiusz Miśkiewicz wrote:
Bug report:
When using dovecot 2.2.25 SNI capability it doesn't always match proper vhost config. For example if we have such config:
local_name imap.example.com { ssl_cert = </etc/certs/cert.imap.example.com.pem ssl_key = </etc/certs/cert.imap.example.com.pem }
but imap client sends mixedcase SNI hostname like "IMAP.example.com" then dovecot won't match above local_name imap.example.coml config section.
IMO dovecot should do case insensitive comparison. Case sensitive matching for DNS names makes little sense.
Hi!
Thank you for reporting this, we'll look into it.
Aki Tuomi Dovecot oy
On 13.10.2016 16:09, Arkadiusz Miśkiewicz wrote:
Bug report:
When using dovecot 2.2.25 SNI capability it doesn't always match proper vhost config. For example if we have such config:
local_name imap.example.com { ssl_cert = </etc/certs/cert.imap.example.com.pem ssl_key = </etc/certs/cert.imap.example.com.pem }
but imap client sends mixedcase SNI hostname like "IMAP.example.com" then dovecot won't match above local_name imap.example.coml config section.
IMO dovecot should do case insensitive comparison. Case sensitive matching for DNS names makes little sense.
Hi!
Fixed in https://github.com/dovecot/core/commit/c19c44f87ef3fe40cae4be9a86ee9327a7370...
Aki Tuomi Dovecot oy
participants (2)
-
Aki Tuomi
-
Arkadiusz Miśkiewicz