test-bleichenbacher-timing-marvin: ServerHello: unexpected extension server_name when using DNS-based hostname about tlsfuzzer HOT 5 CLOSED

Thank you :) Yep, the pregenerate script works as expected!

from tlsfuzzer.

Right, because the test case is strict with the expected extensions, it fails when the server echoes back the server_name extension. Actually, better workaround is to use the --no-safe-renego option, as that will enable the automatic processing of extensions in ServerHello.

That being said, why you're running test-bleichenbacher-timing-marvin.py script? As it's documented, it's valid only for testing TLS servers that use Marvin workaround internally:

AFAIK, at this time, it's just Mozilla NSS that does that. All the other servers should be tested with test-bleichenbacher-timing-pregenerate.py

from tlsfuzzer.

should be fixed with #896

from tlsfuzzer.

Thanks @tomato42.

Related to this:

That being said, why you're running test-bleichenbacher-timing-marvin.py script? As it's documented, it's valid only for testing TLS servers that use Marvin workaround internally:

Yep, this was operator error on my behalf; I hadn't double-checked the filename of the script to run, and incorrectly chose the one that had marvin in the name.

from tlsfuzzer.

ah, ok. Well, I fixed it in both scripts, so feel free to use the ...-pregenerate.py that will handle server_name correctly :)

from tlsfuzzer.