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

Client Hello aead_id issue. #289

Closed
samfr-lol opened this issue Jan 30, 2025 · 1 comment · Fixed by #290
Closed

Client Hello aead_id issue. #289

samfr-lol opened this issue Jan 30, 2025 · 1 comment · Fixed by #290

Comments

@samfr-lol
Copy link

Describe the bug
The aead_id seems to be randomized between ChaCha20Poly1305 and AES-128-GCM when with chrome and edge it should ONLY be AES-128-GCM .

To Reproduce
Steps to reproduce the behavior:

session := azuretls.NewSession()
session.InsecureSkipVerify = true
session.Browser = azuretls.Chrome
session.GetClientHelloSpec = azuretls.GetLastChromeVersion

Make a request to https://tls.browserleaks.com/ with the session created.

Expected behavior
I expected the aead_id to only be AES-128-GCM rather than a mix between ChaCha20Poly1305 and AES-128-GCM

Screenshots

Image
Image

Desktop (please complete the following information):

  • OS: Windows
  • Browser: chrome
  • Version: 131
@Noooste
Copy link
Owner

Noooste commented Jan 31, 2025

Hello, thank you for this report! This problem will be corrected as soon as possible!

@Noooste Noooste linked a pull request Jan 31, 2025 that will close this issue
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

Successfully merging a pull request may close this issue.

2 participants