Bug#421446: [pkg-fetchmail-maint] Bug#421446: fetchmail: Invalid SSL protocol '' specified, using default (SSLv23).

[Nico Golde]

tags 421446 + confirmed upstream pending

Hi,
* Holger Leskien <holger at leskien.com> [2007-04-29 13:00]:
> Since the update to stable (etch) I get the following error message:
> 
> Invalid SSL protocol '' specified, using default (SSLv23).
> 
> My .fetchmailrc:
> 
> set no bouncemail
> set syslog
> poll sslserver.example.com proto POP3
>     user "xxxxxxxx" pass "xxxxxxxx"
>     ssl
>     fetchall
> 
> There is no combination of "sslproto ssl2", "sslproto SSL2", "sslproto
> ssl3", etc... which silences the message. Others seem to have the same
> problem:
[...]
Looks like the documentation is wrong here:
	if(myproto) {
		if(!strcasecmp("ssl2",myproto)) {
			_ctx[sock] = SSL_CTX_new(SSLv2_client_method());
		} else if(!strcasecmp("ssl3",myproto)) {
			_ctx[sock] = SSL_CTX_new(SSLv3_client_method());
		} else if(!strcasecmp("tls1",myproto)) {
			_ctx[sock] = SSL_CTX_new(TLSv1_client_method());
		} else if (!strcasecmp("ssl23",myproto)) {
			myproto = NULL;
		} else {
			fprintf(stderr,GT_("Invalid SSL protocol '%s' specified, using default (SSLv23).\n"), myproto);
			myproto = NULL;
		}
	}

So you have to use ssl2,ssl3,ssl23.
I talk with upstream about patching the manpage.
Kind regards
Nico

-- 
Nico Golde - http://ngolde.de - nion at jabber.ccc.de - GPG: 0x73647CFF
For security reasons, all text in this mail is double-rot13 encrypted.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/pkg-fetchmail-maint/attachments/20070429/32160135/attachment.pgp