Closed elukey closed 5 years ago
This test case is triggering a TLSv1.2 renegotiation by changing the cipher and checks that it is properly denied for h2.
Since TLSv1.3 does use a separte cipher suite, this configuration does not trigger anything and the request goes through normally. I think the test suite should skip this, or force 1.2.
WDYT?
+1 it seems sound!
Is the 404 expected as well? I get the 403 in this case, but not the latter.. (sorry I might miss something obvious).
Yes, I think 404 is correct. It's a Location without any mapping.
I just noticed the /renegotiate/cipher/
vs /renegotiate/cipher
, ok now it makes sense :D
Getting back to this.. Would it be possible with the current setup to force TLS 1.2? Because from what I can see curl supports --tls12 that is for TLS 1.2+ (so even 1.3 if available).
Thanks for the PR that fixed this!
Hi!
I can't make the
test_101_ssl_reneg.py
test to succeed on Debian Buster / Ubuntu Bionic. I tried to debug a bit the problem, and I was a bit puzzled by the second failure, that ends up in a HTTP 404 rather than a HTTP 403.I haven't been able to test this on a system with TLS 1.2 only. I may be related to TLS 1.3 and renegotiation but I didn't find a clear proof in the logs.
The httpd code that I am testing is the last version of 2.4.x (including mod_h2). I am probably missing something obvious, in case apologies in advance for the noise :)