Re: dovecot 2.2.25 BUG: local_name is not matching correctly

2016-10-17 Thread Aki Tuomi



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 = 

Hi!

Fixed in 
https://github.com/dovecot/core/commit/c19c44f87ef3fe40cae4be9a86ee9327a7370e46


Aki Tuomi
Dovecot oy


Re: dovecot 2.2.25 BUG: local_name is not matching correctly

2016-10-13 Thread Aki Tuomi


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 =  ssl_key =  }
>
> 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


dovecot 2.2.25 BUG: local_name is not matching correctly

2016-10-13 Thread Arkadiusz Miśkiewicz

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 =