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

Proposal: Support HTTP2 fingerprint #1071

Closed
deancn opened this issue Aug 21, 2022 · 1 comment · Fixed by #1072
Closed

Proposal: Support HTTP2 fingerprint #1071

deancn opened this issue Aug 21, 2022 · 1 comment · Fixed by #1072
Labels
enhancement New feature or request
Projects

Comments

@deancn
Copy link
Contributor

deancn commented Aug 21, 2022

Is your feature request related to a problem? Please describe.
In recent years, cyber security is facing more and more issues, as a gateway component, BFE should consider and improve the security part.
We can see BFE already integrated with ja3(salesforce), it's very good. But ja3 can be impersonated easier and easier

We found a good solution - http2fingerprint(akamai) this year, and i have already used it. so I propose to implement it in BFE.
Demo: https://privacycheck.sec.lrz.de/passive/fp_h2/fp_http2.html#fpDemoHttp2

Describe the solution you'd like

Describe alternatives you've considered

Additional context
Reference Paper:
https://www.blackhat.com/docs/eu-17/materials/eu-17-Shuster-Passive-Fingerprinting-Of-HTTP2-Clients-wp.pdf

A simple implement by @xqbumu:
#1072

@xqbumu
Copy link
Contributor

xqbumu commented Aug 22, 2022

here is an initial implementation:

https://github.com/xqbumu/bfe/compare/4f815116..feat/h2fp

@iyangsj iyangsj added this to To do in BFE 1.0 via automation Aug 28, 2022
@iyangsj iyangsj added the enhancement New feature or request label Aug 28, 2022
BFE 1.0 automation moved this from To do to Done Sep 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
BFE 1.0
  
Done
Development

Successfully merging a pull request may close this issue.

3 participants