Bug 999899

Description of problem:

imapsync no longer works under CentOS 5 when using SSL connections.


Version-Release number of selected component (if applicable):

Problem exists with versions 1.547 and 1.555 under CentOS 5 (the problem does not occur under CentOS 6).

Last version where the problem did not occur was 1.542.


How reproducible:

Execute imapsync using SSL encryption on any side (--ssl1 or --ssl2).


Steps to Reproduce:

1. Call the tool with --ssl1 (and some switch that does something, like --version)


Actual results:

[jonas@lyra ~]$ imapsync --ssl1 --version
Undefined subroutine &IO::Socket::SSL::set_ctx_defaults called at /usr/bin/imapsync line 4327.


Expected results:

imapsync should work as it worked before. Here's the same command executed on a CentOS 6 host where the problem does not occur:

[jonas@andromeda ~]$ imapsync --ssl1 --version
1.555


Additional info:

Using perl-IO-Socket-SSL-1.01-2.el5 which is the most current version on CentOS 5.

Looking at the ChangeLog ...

http://cpansearch.perl.org/src/SULLR/IO-Socket-SSL-1.953/Changes

... it seems like set_ctx_defaults has been introduced with v1.14 (2011-05-09) and deprecated with v1.81 (2012-12-06). In any case, the IO::Socket::SSL version of CentOS 5 is ways too old to support that function that is obviously now needed by imapsync.

The incompatibility seems to be introduced with imapsync 1.543, judging from its changelog:

revision 1.543
date: 2013/05/22 01:22:03;  author: gilles;  state: Exp;  lines: +12 -7
SSL_verify_mode 0 to avoid warning about Man-In-The-Middle. 

The code in question is this:

        if ( $ssl1 or $ssl2 or $tls1 or $tls2 ) {
                require IO::Socket::SSL ;
                #$IO::Socket::SSL::DEBUG = 3 ;
                IO::Socket::SSL::set_ctx_defaults( 
                        SSL_verify_mode => 0,
                );
        }

Commenting out the set_ctx_default call seems to solve the problem, however I'm not sure if this is a good idea.