Mailing List Archive: [Bug 3077] Munge GnuTLS messages in test suite

https://bugs.exim.org/show_bug.cgi?id=3077

Jeremy Harris <jgh146exb@wizmail.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|Exim 4.97 |Exim 4.98
Version|N/A |4.97
Assignee|unallocated@exim.org |jgh146exb@wizmail.org

--- Comment #1 from Jeremy Harris <jgh146exb@wizmail.org> ---
I can't find the context around that patch addition, in my "runtest" here.

Also:

- the "Have channel bindings cached" looks like OpenSSL only, not present
in tls-gnu.c in my code here (I'm tempted to drop those pointers from that
debug
line in tls-openssl.c)

- I don't see 'server generated X25519 shared' in any of the current "golden
output"
files under test/

Are we looking at different codebases? Different TLS library versions?

--
You are receiving this mail because:
You are on the CC list for the bug.

--
## subscription configuration (requires account):
## https://lists.exim.org/mailman3/postorius/lists/exim-dev.lists.exim.org/
## unsubscribe (doesn't require an account):
## exim-dev-unsubscribe@lists.exim.org
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/

https://bugs.exim.org/show_bug.cgi?id=3077

Andrew Aitchison <exim@aitchison.me.uk> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED

--- Comment #2 from Andrew Aitchison <exim@aitchison.me.uk> ---
GnuTLS 3.8.1-4ubuntu1.2

Ah. The patch was against my own patched version, which already had:
+ 'tls_debug' =>
+ {
+ 'stderr' =>
+ 's/tls_write\(0x[0-9a-f]*,/tls_write\(0xdeadbeef,/;
+ s/SSL_read\(0x[0-9a-f]*, 0x[0-9a-f]*,/SSL_read\(0xdeadbeef,
0xdeadbeef,/;
+ s/SSL_write\(0x[0-9a-f]*, 0x[0-9a-f]*,/SSL_write\(0xdeadbeef,
0xdeadbeef,/;
+ s/(_SECRET(_[0-9])?) [0-9a-f]{64} [0-9a-f]{96}/$1 64hexdigits
96hexdigits/;
+ s/(Have channel bindings cached for possible auth usage)
0x[0-9a-f]{12} 0x[0-9a-f]{12}/$1 0xdeadbeef, 0xdeadbeef/;
+ ',
+ # 'stdout' => '/^\*{8} Input mismatch \*{8}$/d',
+ },

I had forgotten that I had added that munge option myself.
I see that no existing test has exim -d+tls enabled.

I've closed this for now.
If I end up with a sensible definition for a tls_debug option
(for both tls libraries) I will open a new bug.

--
You are receiving this mail because:
You are on the CC list for the bug.

--
## subscription configuration (requires account):
## https://lists.exim.org/mailman3/postorius/lists/exim-dev.lists.exim.org/
## unsubscribe (doesn't require an account):
## exim-dev-unsubscribe@lists.exim.org
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/