Re: [Dovecot] How to disable SSL and TLSv1.1?
Hi Noel, On 09/12/2013 08:54 AM, Noel Butler wrote: [snip] I'm always of the belief that if one person wants a feature, they might be the only vocal person, but they are never really alone, so post your patch, Timo can only either pull it in, or decline it, as for its useful for others, only time will tell, but not even god will help those who use it on a commercial network with paying customers - thats just plain professional suicide. Unless it was clearly stated what the requirements are when they sign up. With NIST sleeping at the helm and the NSA having a field day it would not surprise me if businesses understand the importance of stronger encryption. Regards, Patrick
Re: [Dovecot] Understanding Sockets
On 12/22/2012 09:50 AM, Reindl Harald wrote: because they are too lazy to lern how tu buld packages for their distribution which is at least for redhat-based distribution trivial Calling people lazy is a bit over the top now isn't it? The reason that organizations use Red Hat RHEL is, among other things, support. And Red Hat only supports what they ship. The ability to create an RPM of the latest version is not the issue. Loosing support for that piece of software because you rolled your own is. Regards, Patrick
Re: [Dovecot] IPv6 & SSL
On 10/06/2012 12:02 PM, Patrick Westenberg wrote: Hi Luigi, with regard to SSL my configuration is much more simple and it works fine with IPv4 and IPv6. But you have of course to use a hostname matching the certificates common name. You could add additional hostnames in the certificate by specifying them in SubjectAltName. I use that so my certificate works with both the public FQDN going over the Internet as well as the internal hostname when using a VPN or on the local LAN. Regards, Patrick