[PR #186] [MERGED] Update browser fingerprints #286

New issue

Closed

opened 2026-02-26 12:34:30 +03:00 by kerem · 0 comments

kerem commented

2026-02-26 12:34:30 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/cbeuw/Cloak/pull/186
Author: @HirbodBehnam
Created: 3/23/2022
Status: ✅ Merged
Merged: 3/31/2022
Merged by: @cbeuw

Base: master ← Head: master

📝 Commits (2)

f67ae6e Update chrome fingerprint
9614fbc Update firefox fingerprint

📊 Changes

4 files changed (+32 additions, -26 deletions)

View changed files

📝 internal/client/chrome.go (+11 -9)
📝 internal/client/chrome_test.go (+1 -1)
📝 internal/client/firefox.go (+18 -14)
📝 internal/client/firefox_test.go (+2 -2)

📄 Description

Hello
This issue will fix issue #185
I simply used https://tlsfingerprint.io/ to match cloak's fingerprint with chrome.
There were two changes. At first I dropped TLS 1.0 and 1.1 in client hello. Then I added application settings field to client hello. This holds a value about ALPN. I'm not sure but this might break some other stuff. (The cloak direct connection works fine in Iran)
Also here is a proof from tlsfingerprint.io that shows cloak's fingerprint which is the same as chrome:

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/cbeuw/Cloak/pull/186 **Author:** [@HirbodBehnam](https://github.com/HirbodBehnam) **Created:** 3/23/2022 **Status:** ✅ Merged **Merged:** 3/31/2022 **Merged by:** [@cbeuw](https://github.com/cbeuw) **Base:** `master` ← **Head:** `master` --- ### 📝 Commits (2) - [`f67ae6e`](https://github.com/cbeuw/Cloak/commit/f67ae6e644318ecfc1d24d4c9b5ee3034548f750) Update chrome fingerprint - [`9614fbc`](https://github.com/cbeuw/Cloak/commit/9614fbc03d2f45eac774d42c9552ab8cd0084783) Update firefox fingerprint ### 📊 Changes **4 files changed** (+32 additions, -26 deletions) <details> <summary>View changed files</summary> 📝 `internal/client/chrome.go` (+11 -9) 📝 `internal/client/chrome_test.go` (+1 -1) 📝 `internal/client/firefox.go` (+18 -14) 📝 `internal/client/firefox_test.go` (+2 -2) </details> ### 📄 Description Hello This issue will fix issue #185 I simply used https://tlsfingerprint.io/ to match cloak's fingerprint with chrome. There were two changes. At first I dropped TLS 1.0 and 1.1 in client hello. Then I added `application settings` field to client hello. This holds a value about ALPN. I'm not sure but this might break some other stuff. (The cloak direct connection works fine in Iran) Also here is a proof from tlsfingerprint.io that shows cloak's fingerprint which is the same as chrome: ![image](https://user-images.githubusercontent.com/11520090/159760481-ccc329b0-6b98-4908-b587-12ab2d1c8098.png) ![image](https://user-images.githubusercontent.com/11520090/159760514-ce975fe4-3750-4e1a-84d0-3b6c3526e41b.png) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

kerem

2026-02-26 12:34:30 +03:00

closed this issue
added the
pull-request
label

No labels

pull-request

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/Cloak#286

No description provided.

Rows
Columns