TLS Fingerprint основная проблема BAS

[ranjeet]

@sergerdn
i am not chromium devloper me be some deatils will wrong becuse i am using ai for research only i am tried to under stand how chromium genrating tsl fb.
i am 4mohtn after devloped my won proxy network with tsl spoofing but my account are still banning i am using total humen for page visit and do task

[Int64]

@rsgmsk said in TLS Fingerprint основная проблема BAS:

TLS отпечаток он разный у людей

@rsgmsk said in TLS Fingerprint основная проблема BAS:

одинаковый tls отпечаток это палево

Не путай теплое с мягким:

• настройки HTTP-клиента браузера (TLS-отпечаток, порядок расширений, заголовки)
• JS/device-fingerprint (canvas, WebGL, шрифты и т.д.)

Представь что TLS-отпечаток - это как SHA256(версия браузера/приложения/User-Agent).
Одинаковый TLS-отпечаток говорит, что клиент ведёт себя как оригинальная версия браузера/приложения и не конфликтует например с User-Agent

[Int64]

@ranjeet said in TLS Fingerprint основная проблема BAS:

but I could not do it

And all this time, my finished module was already on the forum))

https://community.bablosoft.com/topic/30528/http-client-curl-impersonate-http-2-tls-1-3-browser_presets-websocket

[tersinemuhendis]

@Int64 bad library.

[Int64]

@tersinemuhendis any proof?

[ranjeet]

I’ve started studying low-level networking to understand full network behavior in depth. The clear conclusion so far is that a TLS fingerprint cannot be formed solely by BAS (Chromium). TLS fingerprinting also depends on system-level OS behavior, where the browser + OS + network stack + hardware timing together create the final observable fingerprint.

In this process, the protocol-level fingerprint (from Chrome/Chromium) stays consistent, but OS-level packet timing, TCP implementation, congestion control, jitter, and data buffering influence the actual TLS identity.

I do see one possible direction — but this would require building a larger ecosystem where the proxy environment can either emulate or preserve OS-level network characteristics. That’s ongoing R&D, and we’ll see how it evolves.

At least one confusion is now clearly resolved: as per my current knowledge, modifying only BAS (Chromium) to produce different realistic TLS fingerprints does not seem practically feasible unless the OS-level signals are also replicated or manipulated.

(all are translated hindi to english )

[tersinemuhendis]

@Int64 https://github.com/0x676e67/rnet good tls library.

[Int64]

@tersinemuhendis My module is the same)

[dnffl0019]

отличная информация, спасибо, ребята!

[tersinemuhendis]

@Int64 Having the same boardingssl doesn't mean you're doing the same operations, my friend. Chrome also uses boardingssl, so that doesn't mean your module works the same with Chrome.

[Int64]

@tersinemuhendis omg 😲 read the module description carefully or give me real facts

[usertrue]

@Int64 пусть изобретают свой велосипед, не трать время на них.

[sergerdn]

@usertrue said in TLS Fingerprint основная проблема BAS:

@Int64 пусть изобретают свой велосипед, не трать время на них.

//режим старпера on
Люди слишком доверяют своему мнению, если взять и проверить снаружи свою гипотезу, то будет в сразу видно что происходит.
//режим старпера off