Add (kind of) support for loading a list of JA4C malicious fingerprints #2678
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
IvanNardi
force-pushed
the
malicious_fingerprint_to_ja4
branch
from
0018ce6 to
afa1a68
Compare
IvanNardi
force-pushed
the
malicious_fingerprint_to_ja4
branch
from
afa1a68 to
88bf4f8
Compare
It might be usefull to be able to match traffic against a list of suspicious JA4C fingerprints Use the same code/logic/infrastructure used for JA3C (note that we are going to remove JA3C...) See: ntop#2551
IvanNardi
force-pushed
the
malicious_fingerprint_to_ja4
branch
from
88bf4f8 to
d5abbb8
Compare
|
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.
It might be usefull to be able to match traffic against a list of suspicious JA4C fingerprints
Use the same code/logic/infrastructure used for JA3C (note that we are going to remove JA3C...)
See: #2551