[exim-dev] [Bug 1455] tls_out_cipher is empty

Startseite
Nachricht löschen
Nachricht beantworten
Autor: Andreas Metzler
Datum:  
To: exim-dev
Betreff: [exim-dev] [Bug 1455] tls_out_cipher is empty
------- You are receiving this mail because: -------
You are on the CC list for the bug.

http://bugs.exim.org/show_bug.cgi?id=1455




--- Comment #2 from Andreas Metzler <eximusers@???> 2014-03-30 18:48:02 ---
On 2014-03-30 Jeremy Harris <jgh146exb@???> wrote:
> ------- You are receiving this mail because: -------
> You reported the bug.


> http://bugs.exim.org/show_bug.cgi?id=1455


> Jeremy Harris <jgh146exb@???> changed:


>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>              Status|NEW                         |RESOLVED
>          Resolution|                            |WORKSFORME


> --- Comment #1 from Jeremy Harris <jgh146exb@???> 2014-03-30 17:13:29 ---
> I modified testsuite case 3465 with headers_add for tls_out_cipher and
> tls_cipher on the transport, and -d-all+deliver+transport+tls on the script for
> the first queue-run. Debug output shows the expected tls_out_cipher header
> being added (matching the tls connection setup) and an empty tls_cipher.


Did you test with OpenSSL or GnuTLS?

I am not sure what is happening, yesterday when I tested
$tls_out_cipher expanded to an empty string, and today I get the
behavior you described.

However I am quite sure I was not halluzinating yesterday.

Also the behavior you (and me) experienced today is broken, too. While
tls_cipher is deprecated, it still should work and is documented to
be. It must not expand to an empty string.

cu Andreas


--
Configure bugmail: http://bugs.exim.org/userprefs.cgi?tab=email