hould do it.
I have seen that a bug that is probably rootet in this has been posted
here before regarding ssl3-disabled configs:
http://dovecot.org/pipermail/dovecot/2015-March/100188.html
cu,
--
Hanno Böck
http://hboeck.de/
mail/jabber: ha...@hboeck.de
GPG: BBB51E42
--- ./dovecot-2.2.16-va
a, 2.2.16) on a Gentoo.
Please note that it's not dovecot itself that's crashing but
pop3-login/imap-login. You don't note these if you haven't some kind of
segfault reporting.
--
Hanno Böck
http://hboeck.de/
mail/jabber: ha...@hboeck.de
GPG: BBB51E42
pgpJw2zezMDy6.pgp
that.
You just need to *disable* SSLv3, but that can be done within the
config file.
--
Hanno Böck
http://hboeck.de/
mail/jabber: ha...@hboeck.de
GPG: BBB51E42
pgp6z5bjXKq0y.pgp
Description: OpenPGP digital signature
e attached patch.
I found this by compiling dovecot with address sanitizer and running
the test suite.
cu,
--
Hanno Böck
http://hboeck.de/
mail/jabber: ha...@hboeck.de
GPG: BBB51E42
--- ./dovecot-2.2.18/src/lib/wildcard-match.c 2014-08-20 11:47:58.0 +0200
+++ ./dovecot-2.2.18-patch/src/li
se.
I haven't found an easy way to detect that. The easiest thing would be
if there'd be a way to add the port number to the pop3-login/imap-login
lines in the log files. Any way to do that?
cu,
--
Hanno Böck
http://hboeck.de/
mail/jabber: ha...@hboeck.de
GPG: BBB51E42
signature.asc
Description: PGP signature
probably unexpected side-effect.
Maybe this is related to the DDoS-protection measures that have been
added in dovecot 2.2.13.
Would apprechiate if someone could have a look.
cu,
--
Hanno Böck
http://hboeck.de/
mail/jabber: ha...@hboeck.de
GPG: BBB51E42
signature.asc
Description: PGP signature
more robust and work independently of the
version number of the used openssl instance.
cu,
--
Hanno Böck
http://hboeck.de/
mail/jabber: ha...@hboeck.de
GPG: BBB51E42
diff -Naur dovecot-2.2.13/src/lib-ssl-iostream/iostream-openssl-context.c dovecot-2.2.13-1/src/lib-ssl-iostream/iostream-openssl-c
