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

Signature_algorithms extension configuration and parsing logic are inconsistent #24

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

Comments

@huiyuexu
Copy link

huiyuexu commented Oct 11, 2023

Issue Type: Tool Configuration

Testcase name: signature_algorithms extension

Testcase number: TLS_B1_GP_03_T

Test code: TLS_B1_GP_03_T.java

Description:
In TestRunPlan mode and TLS 1.2 tested, only reserverd_4 can be configured in the XML file to configure algorithm as rsa_pss_rsae_sha256. Otherwise, the tool cannot send expected packets carrying rsa_pss_rsae_sha256 algorithm.

However, when parsing the received packets, the parsed result is rsa_pss_rsae_sha256 (as expected), which is different from reserverd_4 configured in the XML file. As a result, the test case is failed.

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