This repository has been archived by the owner on Dec 6, 2023. It is now read-only.
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.
Changes since 1.0:
Add serverkeyreplace TLS/SSL attack to test that clients verify that the
server possesses the private key corresponding to the SSL certificate
that was presented to the client.
Data handlers that can modify the connection data are now run
probabilistically with the same probability as set with -p or by the
client. Passive detection handlers will still run on all connections.
Nogotofail clients will now receive vulnerability notifications when
HTTP is detected. To prevent spamming the Android client supports muting
on a per (application, vulnerability) level.
Removed the -a and -v nogotofail.mitm flags and made them default.
The -b and -q flags were added to bridge all connections from
non-clients and limit logging respectively.
Improved connection throughput and make calls to the nogotofail clients
non-blocking.
Improved robustness of earlyCCS TLS/SSL attack.
Added a basic android test app under nogotofail/test/android with a
handful of vulnerabilities.