-
Notifications
You must be signed in to change notification settings - Fork 16
Fix bugs in _security_tls_v1_2_server #1248
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
Merged
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
fd2efb5
fix tls bugs, added unit tests for tls 1.2 server test
cda95c2
Merge branch 'dev' of https://github.com/MariusBaldovin/testrun into …
574a0b2
uncomment tls tests
7101ea3
uncomment tls test
fc91264
corrected if the tls 1.2 is invalid and 1.3 is valid
1d0468d
Merge branch 'dev' into bug/tls
jboddey File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TLS 1.3 can still validate TLS 1.2. If a device is running just TLS 1.3, it shouldn't fail TLS 1.2 since the requirement is at least TLS 1.2 for this test so there should be no need for this additional check.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
_tls_util.process_tls_server_results is causing a bug. When TLS 1.2 is not supported the TLS 1.3 will incorrectly validate/invalidate 1.2 (#1228). With these changes when TLS 1.2 is not supported the test result will be "Feature not detected" and since this test is "Required if Applicable" it will not affect the overall test result. The TLS 1.3 will still validate TLS 1.2 but only when 1.2 is non compliant and 1.3 is compliant (line 374). Also the description will mention that tls 1.2 cert is invalid but 1.3 is valid. I have added unit tests for all use cases for _security_tls_v1_2_server.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That bug is only if TLS 1.3 is invalid and TLS 1.2 is valid so this still needs to check both TLS 1.2 and 1.3 in the 1.2 test but not fail if TLS 1.2 is valid but not 1.3. This needs to be fixed in the validation logic, not removing that scenario from being tested.