Courier IMAP SSL broken after update

Automatically imported from Debian bug report #333896 http://bugs.debian.org/333896

Message-ID: <email address hidden>
Date: Fri, 14 Oct 2005 12:49:37 +0200
From: Yonatan Feldman <email address hidden>
To: <email address hidden>
Cc: <email address hidden>, Yonatan Feldman <email address hidden>
Subject: Courier IMAP SSL broken after update

------=_Part_13407_1507494.1129286977338
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Package: courier-ssl

After performing a standard update using apt-get and dselect I can no
longer connect to my SSL Courier IMAP server.

I get the following error from mutt:

    gnutls_handshake: A TLS packet with unexpected length was received.

I ran the "gnutls-cli-debug -v -p 993 mail.milliped.com" and got the
following output:

    Resolving 'mail.milliped.com'...
    Connecting to '66.59.109.158:993'...
    Checking for TLS 1.1 support... no
    Checking fallback from TLS 1.1 to... failed
    Checking for TLS 1.0 support... no
    Checking for SSL 3.0 support... no

    Server does not support none of SSL 3.0, TLS 1.0 and TLS 1.1

How can I restore SSL/TLS support?

I have attached a log of the update output from the terminal

Thanks,
yon.

------=_Part_13407_1507494.1129286977338
Content-Type: text/plain; name="debian broekn update.txt"; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="debian broekn update.txt"

[macondo:~] apt-get update; apt-get upgrade
Get:1 http://http.us.debian.org unstable Release.gpg [189B]
Hit http://http.us.debian.org unstable Release
Hit http://http.us.debian.org unstable/main Packages
Hit http://http.us.debian.org unstable/contrib Packages
Hit http://http.us.debian.org unstable/non-free Packages
Get:2 http://debian.teleglobe.net unstable/non-US Release.gpg [197B]
Hit http://debian.teleglobe.net unstable/non-US Release
Ign http://debian.teleglobe.net unstable/non-US Release
Ign http://debian.teleglobe.net unstable/non-US/main Packages
Ign http://debian.teleglobe.net unstable/non-US/contrib Packages
Ign http://debian.teleglobe.net unstable/non-US/non-free Packages
Hit http://debian.teleglobe.net unstable/non-US/main Packages
Hit http://debian.teleglobe.net unstable/non-US/contrib Packages
Hit http://debian.teleglobe.net unstable/non-US/non-free Packages
Fetched 198B in 2s (82B/s)
Reading package lists... Done
W: GPG error: http://debian.teleglobe.net unstable/non-US Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B629A24C38C6029A
W: You may want to run apt-get update to correct these problems
Reading package lists... Done
Building dependency tree... Done
The following packages have been kept back:
  bind9-host courier-ssl dnsutils initscripts libapache-mod-php4 libdns20 libpq3 libreadline5 mutt netbase openssh-client
  openssh-server openssl php4 php4-cli php4-common php4-pear postgresql-7.4 postgresql-client-7.4 sysvinit wget
The following packages will be upgraded:
  courier-authdaemon courier-base courier-imap courier-imap-ssl dash debianutils dictionaries-common info libacl1 libattr1
  libbind9-0 libisc9 libisccc0 libisccfg1 liblwres1 lib...

Message-ID: <email address hidden>
Date: Fri, 14 Oct 2005 13:31:18 +0200
From: Stefan Hornburg <email address hidden>
To: Yonatan Feldman <email address hidden>, <email address hidden>
Subject: Re: Bug#333896: Courier IMAP SSL broken after update

Yonatan Feldman wrote:

>Package: courier-ssl
>
>After performing a standard update using apt-get and dselect I can no
>longer connect to my SSL Courier IMAP server.
>
>I get the following error from mutt:
>
> gnutls_handshake: A TLS packet with unexpected length was received.
>
>I ran the "gnutls-cli-debug -v -p 993 mail.milliped.com" and got the
>following output:
>
> Resolving 'mail.milliped.com'...
> Connecting to '66.59.109.158:993'...
> Checking for TLS 1.1 support... no
> Checking fallback from TLS 1.1 to... failed
> Checking for TLS 1.0 support... no
> Checking for SSL 3.0 support... no
>
> Server does not support none of SSL 3.0, TLS 1.0 and TLS 1.1
>
>How can I restore SSL/TLS support?
>
>I have attached a log of the update output from the terminal
>
>
That looks similar to bug #333788.

Bye
       Racke

Message-ID: <email address hidden>
Date: Mon, 24 Oct 2005 20:55:20 +0200
From: Stefan Hornburg <email address hidden>
To: <email address hidden>
Subject: Merge and reassign courier-ssl problems

reassign 334920 courier-ssl
severity 334920 grave
reassign 335512 courier-ssl
retitle 335512 certificate problem: DLFCN_LOAD:could not load the shared library
severity 333896 grave
merge 334920 335512 333896

*** Bug 24537 has been marked as a duplicate of this bug. ***

*** Bug 24552 has been marked as a duplicate of this bug. ***

Message-ID: <email address hidden>
Date: Mon, 24 Oct 2005 15:41:41 -0700
From: Steve Langasek <email address hidden>
To: Russel Winder <email address hidden>, <email address hidden>
Subject: Re: Bug#335512: courier-imap-ssl: 2004-10-24 Testing update causes imap ssl to cease working

--sgneBHv3152wZ8jf
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

block 335512 by 335271
thanks

On Mon, Oct 24, 2005 at 12:56:59PM +0100, Russel Winder wrote:
> Package: courier-imap-ssl
> Version: 3.0.8-11
> Severity: grave
> Justification: renders package unusable

> I run Debian GNU/Linux Testing. My courier IMAP SSL system was
> working fine. I upgraded this morning 2005-10-24 and now for every
> attempted connection, I get:

> Oct 24 12:26:44 dimen imapd-ssl: couriertls: /etc/courier/imapd.pem:
> error:25066067:DSO support routines:DLFCN_LOAD:could not load the
> shared library

Yes, this error has been reported against several other packages already,
and appears to be a regression in libssl0.9.8. Apologies for not catching
this before it reached testing.

--=20
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
<email address hidden> http://www.debian.org/

--sgneBHv3152wZ8jf
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDXWMlKN6ufymYLloRAtpUAKCP4yWVpCK4wJ/zUAF7Ri+4OqtfLACfTvB2
MtMMsD9L4Inj3ywqSPzu54Q=
=mCO7
-----END PGP SIGNATURE-----

--sgneBHv3152wZ8jf--

Message-Id: <email address hidden>
Date: Tue, 25 Oct 2005 09:57:56 +0200
From: Stefan Hornburg <email address hidden>
To: <email address hidden>
Cc: <email address hidden>

tags 333896 + confirmed
tags 334920 + confirmed
tags 335512 + confirmed

--
LinuXia Systems => http://www.linuxia.de/
Expert Interchange Consulting and System Administration
ICDEVGROUP => http://www.icdevgroup.org/
Interchange Development Team

Message-Id: <email address hidden>
Date: Tue, 25 Oct 2005 17:33:42 -0700
From: Steve Langasek <email address hidden>
To: <email address hidden>
Subject: unblock 333896 with 335510, unblock 334920 with 335510, unblock 335512 with 335510

# Automatically generated email from bts, devscripts version 2.9.7
unblock 333896 with 335510
unblock 334920 with 335510
unblock 335512 with 335510

Message-ID: <email address hidden>
Date: Sun, 30 Oct 2005 17:28:47 +0100
From: Kurt Roeckx <email address hidden>
To: <email address hidden>
Subject: Re: dovecot-imapd does not load shared libraries or ssl certs

reassign 336140 libpq4
block 333896 by 336140
block 334920 by 336140
block 335512 by 336140
unblock 333896 by 335271
unblock 334920 by 335271
unblock 335512 by 335271
merge 336140 334180
thanks

I hope this does it.

Kurt

Message-ID: <email address hidden>
Date: Wed, 2 Nov 2005 20:27:06 +0100
From: Kurt Roeckx <email address hidden>
To: <email address hidden>
Cc: <email address hidden>
Subject: Re: courier-imap-ssl: DSO support routines:DLFCN_LOAD:could not load the shared library"

reassign 334920 libssl0.9.8 0.9.8-1
close 334920 0.9.8a-3
thanks

I believe all those (merged) bugs should have been fixed by the
new openssl (libssl0.9.8) 0.9.8a-3 upload. Not really sure about
#333896 though.

Please let me know if there are any problems left.

Kurt

No response to upstream request to re-test; we will get the fix via Debian if one comes