[prev in list] [next in list] [prev in thread] [next in thread] 

List:       courier-users
Subject:    Re: [courier-users] OpenSSL crash with STARTTLS in Courier
From:       Sam Varshavchik <mrsam () courier-mta ! com>
Date:       2014-05-05 10:52:51
Message-ID: cone.1399287171.568300.31860.1000 () monster ! email-scan ! com
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


Lindsay Haisley writes:

> On Sun, 2014-05-04 at 14:51 -0400, Sam Varshavchik wrote:
> > Lindsay Haisley writes:
> >
> > > So it looks as if the issue here is that courier is using only SSL/TLS
> > > v2 or v3.  If I spec TLS v1 to couriertls I get, with no errors:
> > >
> > > # TLS_VERIFYPEER=NONE TLS_PROTOCOL=TLS1 couriertls -host=mx.nv.net - 
> port=25 -
> > > protocol=smtp -printx509=2
> >
> > The setting is TLS_PROTOCOL=TLSv1 in the current version.
>
> Courier, as distributed with Ubuntu 12.04 LTS, is at 0.66.1.  That's
> probably not a "current version".
>
> > TLS_PROTOCOL is used for OpenSSL only.
>
> The config file comments appear to specify syntax for both GnuTLS and
> OpenSSL, although this isn't clear.

Config file comments can be misleading when the option's semantics change.  
The sysconftool, that make install runs, does not update the comments. You  
always want to look in the configfile.dist, for the latest, up to date,  
comments.


[Attachment #5 (application/pgp-signature)]

------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
&#149; 3 signs your SCM is hindering your productivity
&#149; Requirements for releasing software faster
&#149; Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce

_______________________________________________
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users


[prev in list] [next in list] [prev in thread] [next in thread]