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

Different understandings of server behavior when the client hello carries compression algorithm #27

Open
huiyuexu opened this issue Oct 11, 2023 · 0 comments

Comments

@huiyuexu
Copy link

Issue Type: Tool Implementation Principle

Testcase name: Compression not selected

Testcase number: TLS_B1_FR_12

Test code: TLS_B1_FR_12.java

Description:
The RFC of TLS 1.2 does not require the behavior (disconnection or ignoring) of handling the client Hello carrying compression algorithm.

However, the tool only allows that server hello packet does not carry compression algorithm after receiving the client hello packet carrying compression algorithm.

We thint if the tested device returns an alert packet and disconnects the TLS connection after receiving the client Hello packet with the compression algorithm, it indicates that the tested device does not select the compression algorithm and meets the requirement. In this case, we think the test case should be PASS.

Looking forward to further discussion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant