Skip to content
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

JA4Server #3

Open
ne4u opened this issue Apr 24, 2024 · 0 comments
Open

JA4Server #3

ne4u opened this issue Apr 24, 2024 · 0 comments
Assignees

Comments

@ne4u
Copy link

ne4u commented Apr 24, 2024

As JA4Server fingerprint relates to this body of work [nginx module], is the intent for nginx to fingerprint itself or fingerprint a proxied endpoint? Fingerprinting the endpoint of nginx proxied connection might prove useful.

Perhaps, there may even be an additional fingerprint standard specifically for HTTP Servers expanding on the JA4S and JA4H concepts that could include:

  • request url hash
  • response header count
  • response header key names hashed
  • response size and status code
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants