forked from tls-attacker/TLS-Scanner
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Master #1
Merged
Merged
Master #1
Conversation
This file contains 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
Allows to scan only for a type of vulnerability without running a full scan
Servers vulnerable to Sweet32 were always marked as not vulnerable
Early exit in the loop when found vulnerable
Reduce the number of rescans to lower the time it takes to scan for padding oracles. From 258sec to 110sec. The number 3 was chosen beacuse this is also what TLS-Attacker uses.
Result of the scan for the Logjam vulnerability was always set to not vulnerable
Report "could not test" in Padding Oracle Probe if it can not execute the test. This can happen if no block ciphers are available
Report "could not test" in Padding Oracle Probe if it can not execute the test. This can happen if no block ciphers are available
In a detailed report the tool did not report if CBC block ciphers were supported and so the recommendation to disable them was never printed out.
Bumps [protocol-toolkit-bom](https://github.com/tls-attacker/Protocol-Toolkit-BOM) from 3.2.5 to 3.2.7. - [Commits](tls-attacker/Protocol-Toolkit-BOM@v3.2.5...v3.2.7) --- updated-dependencies: - dependency-name: de.rub.nds:protocol-toolkit-bom dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
…-protocol-toolkit-bom-3.2.7 build(deps): bump protocol-toolkit-bom from 3.2.5 to 3.2.7
Bumps [protocol-toolkit-bom](https://github.com/tls-attacker/Protocol-Toolkit-BOM) from 3.2.7 to 3.3.0. - [Commits](tls-attacker/Protocol-Toolkit-BOM@v3.2.7...v3.3.0) --- updated-dependencies: - dependency-name: de.rub.nds:protocol-toolkit-bom dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
…-protocol-toolkit-bom-3.3.0 build(deps): bump protocol-toolkit-bom from 3.2.7 to 3.3.0
Scanner-Core is now hosted elsewhere (https://github.com/tls-attacker/Scanner-Core) and has been introduced as an external dependency.
Set new BOM version
Fix compatibility with new TLS-Attacker version
Added missing TlsAnalyzedProperty entries
fixed SNI value set in strictSNI check
…vity http parsing is now case-insensitive
Removed dead code and unused imports
Fixed copy paste bug
Aligned Dockerfile to the Compiling Instructions (https://github.com/tls-attacker/TLS-Scanner?tab=readme-ov-file#compiling). This fixed errors thrown by other Tools which were installed before this (tls-attacker#104)
Simplified Dockerfile by Aligning Dockerfile to the Compiling Instructions
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.