Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

timeout in test-tls13-version-negotiation.py, with v2 ClientHello #452

Open
ueno opened this issue Sep 3, 2018 · 1 comment
Open

timeout in test-tls13-version-negotiation.py, with v2 ClientHello #452

ueno opened this issue Sep 3, 2018 · 1 comment
Labels
bug unintented behaviour in tlsfuzzer code help wanted

Comments

@ueno
Copy link
Collaborator

ueno commented Sep 3, 2018

Bug Report

System Information

Type Version/Name
Operating System Name Fedora
Operating System Version 29
Python version 2.7.15
tlslite-ng version 45e81dc4de6b1c074f1830c2ffa55c4006bfd9a3
tlsfuzzer revision 01f44ce

Problem description

When running tlsfuzzer within NSS upstream CI, the following test gets timeout:

test-tls13-version-negotiation.py:stdout:SSL 2.0 ClientHello with TLS 1.3 version and TLS 1.3 only ciphersuites ...
test-tls13-version-negotiation.py:stdout:Error encountered while processing node <tlsfuzzer.expect.ExpectAlert object at 0x7f00e9857b50> (child: None) with last message being: None
test-tls13-version-negotiation.py:stdout:Error while processing
test-tls13-version-negotiation.py:stdout:Traceback (most recent call last):
test-tls13-version-negotiation.py:stdout:  File "scripts/test-tls13-version-negotiation.py", line 435, in main
test-tls13-version-negotiation.py:stdout:    runner.run()
test-tls13-version-negotiation.py:stdout:  File "/home/dueno/devel/tests_results/security/localhost.1/tlsfuzzer/tlsfuzzer/tlsfuzzer/runner.py", line 200, in run
test-tls13-version-negotiation.py:stdout:    "Timeout when waiting for peer message")
test-tls13-version-negotiation.py:stdout:AssertionError: Timeout when waiting for peer message

Describe how to reproduce the problem

  1. apply the patch from the phabricator to nss trunk
  2. build nss
  3. modify the tlslite-ng commit ID in tests/tlsfuzzer/tlsfuzzer.sh
  4. run the tests

Expected behaviour

The test receives the appropriate alert (decode_error).

@tomato42 tomato42 added bug unintented behaviour in tlsfuzzer code help wanted labels Sep 3, 2018
@tomato42
Copy link
Member

tomato42 commented Sep 3, 2018

this is related to SSLv2 removal, so we need to create a SSLv2 Hello that is a clearly malformed SSLv3 record

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug unintented behaviour in tlsfuzzer code help wanted
Projects
None yet
Development

No branches or pull requests

2 participants