Package: gnutls13 Version: 1.4.4-3 Followup-For: Bug #402665 For what it's worth, I tested for this problem on my setup and did not encounter it. I'm running on an Athlon chip, no Xen (2.4 kernel--see below).
exim4-daemon-heavy 4.63-11 The test consisted of sending a message via /usr/sbin/exim4 -t. The message went out via TLS and then a copy came back (also via TLS, for another system of mine also running the same versions of exim4-daemon-heavy and libgnutls13, but under a 2.6.17 kernel, dual processor Athlon, stock Debian kernel, no Xen). The message made the full round-trip, with the headers showing esmtpsa (TLSv1:AES256-SHA:256) going out (it did not go directly to my other system) and esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) coming in. I hope I continue not to observe it! I don't have a lot of time to help trouble-shoot, but the report got me sufficiently concerned to do the test. I thought I'd pass it on. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (990, 'testing'), (990, 'stable'), (50, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.4.27advncdfs Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]