-
Notifications
You must be signed in to change notification settings - Fork 106
Vk 2052 add ja5 filter #2309
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
Closed
Closed
Vk 2052 add ja5 filter #2309
Conversation
This file contains hidden or 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
We decide to use our own implementation (we call it ja5 hash) for client identification. This patch implement ja5 hash calculation for http layer.
…o vk-2052-add-ja5t-config
We decide to use our own implementation (we call it ja5 hash) for client identification. This patch implement ja5 hash calculation for http layer.
- Move all ja5 constants to separate header file. - Change order of fields according to task description. - Add unit tests. - Move all ja5h cookie calculations, to handle cases when there are several cookie values in one header. - Handle case when cookie or refer header restored from hpack table.
…-2052-add-ja5-filter
We decide to use our own implementation (we call it ja5 hash) for client identification. This patch implement ja5 hash calculation for http layer.
- Move all ja5 constants to separate header file. - Change order of fields according to task description. - Add unit tests. - Move all ja5h cookie calculations, to handle cases when there are several cookie values in one header. - Handle case when cookie or refer header restored from hpack table.
Some headers need extra processing in Tempesta FW source code (we need to set some flags, set some variables and so on). We usually do it when we during parsing headers, but when we restore headers from hpack dynamic table we use special cstate union to save/restore all necessary information. We should zero all state before processing next header.
…-2052-add-ja5-filter
Apply ja5 filter in TLS
const-t
requested changes
Dec 23, 2024
Fixed ja5 config
tls module. Implemented these callbacks in fw.
- fix memory leak during reconfiguration - several codestyle fixes
Co-authored-by: Alexander Krizhanovsky <ak@tempesta-tech.com>
Deadlock occurs if all slots timestamps are greater then end_ts.
We decide to use our own implementation (we call it ja5 hash) for client identification. This patch implement ja5 hash calculation for http layer.
- Move all ja5 constants to separate header file. - Change order of fields according to task description. - Add unit tests. - Move all ja5h cookie calculations, to handle cases when there are several cookie values in one header. - Handle case when cookie or refer header restored from hpack table.
We decide to use our own implementation (we call it ja5 hash) for client identification. This patch implement ja5 hash calculation for http layer.
- Move all ja5 constants to separate header file. - Change order of fields according to task description. - Add unit tests. - Move all ja5h cookie calculations, to handle cases when there are several cookie values in one header. - Handle case when cookie or refer header restored from hpack table.
…pesta into vk-2052-add-ja5-filter
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.
No description provided.