-
Hi :wave: . While working on a personal project that implements JA4, I noticed some discrepancies when comparing JA4 (TCP) fingerprint output against some of the tls PCAP files in your repo.
For ex…
elpy1 updated
1 month ago
-
### Your Feature Request
As we already can leverage JA3 fingerprinting in haproxy to do client fingerprinting.
I would like to see a builtin JA4 hash constant for even better client fingerprinting.…
-
If I have a empty JA4_c, wireshark plugin hashes as e3b0c44298fc while Arkime and the ja4/rust use 000000000000, which is correct?
awick updated
2 weeks ago
-
In https://github.com/komuw/ong/issues/95 (https://github.com/komuw/ong/pull/244) we implemented a TLS fingerprint inspired by ja3.
`ja4+` has been released[1]. `ja4+` has a number of different fi…
komuw updated
10 months ago
-
There exist updates in TLS client fingerprinting technology
https://github.com/FoxIO-LLC/ja4/tree/main
-
Created by Alya Gomaa via monday.com integration. 🎉
-
Hello,
i've run the docker with nginx and i've noticed that only JA4 and JA4L fingerprint are correctly filled (see attached picture). Is it normal? i expect to be also ja4s and ja4h filled. Isn't th…
-
Hi all,
My nginx version is [nginx 1.24.0-2] (from debian testing) and this is my httpd config:
I know that the JA4S depends on the client you use, I used MS Edge (based on chrome). (t13d1516h2_8d…
owah updated
2 months ago
-
### Nuclei version:
latest:v3.2.8
### Current Behavior:
A while back I had [made a discussion on JA3 randomization](https://github.com/projectdiscovery/nuclei/issues/3330) and…
-
It would be great to allow to get raw ja3 fingeprint