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

Disabled tls tickets #48

Open
device-x opened this issue Jan 17, 2023 · 2 comments
Open

Disabled tls tickets #48

device-x opened this issue Jan 17, 2023 · 2 comments

Comments

@device-x
Copy link

device-x commented Jan 17, 2023

Hello. We use nginx with tls tickets for session resumption.

In the nginx patch in the line https://github.com/fooinha/nginx-ssl-ja3/blob/master/patches/nginx.1.23.1.ssl.extensions.patch#L8 ticket support explicitly disabled
Tell me for what and will the module with enabled tls tickets work normally?

Thanks in advance

@device-x device-x changed the title Disables tls tickets Disabled tls tickets Jan 17, 2023
@fooinha
Copy link
Owner

fooinha commented Jan 17, 2023

Naturally, tls tickets being enabled will produce 2 different fingerprint values for the same user-agent, for a series of requests.

Maybe there's a way I could make this configurable.

@gbilic
Copy link
Contributor

gbilic commented Mar 16, 2023

Actually there's the same issue with TLS1.3 session resumption. When the client tries to reuse a psk previously delivered by the server, it adds it in the pre_shared_key (41) extension in the subsequent clientHello resulting in two differents fingerprints. SSL_OP_NO_TICKET does not disable psk generation on server side as stated by Maxim Dounin : https://mailman.nginx.org/pipermail/nginx-devel/2020-April/013092.html
My approach is to treat extension 41 the same way as GREASE to exclude it from fingerprint.

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

3 participants