[GH-ISSUE #4010] TLS Fingerprinting

gitea-mirror commented

2026-05-05 14:03:13 -06:00

Owner

Copy link

Originally created by @dr3adx on GitHub (Feb 20, 2024).
Original GitHub issue: https://github.com/fatedier/frp/issues/4010

Describe the feature request

Hello,

I was wondering how does FRP work in terms of TLS fingerprinting like JA3.
Does it alter the TLS settings at all like cipher suites & extensions? If it does, is there a way I can preserve the original TLS settings?

Any info is appreciated, thank you!

Describe alternatives you've considered

No response

Affected area

Docs
Installation
Performance and Scalability
Security
User Experience
Test and Release
Developer Infrastructure
Client Plugin
Server Plugin
Extensions
Others

Originally created by @dr3adx on GitHub (Feb 20, 2024). Original GitHub issue: https://github.com/fatedier/frp/issues/4010 ### Describe the feature request Hello, I was wondering how does FRP work in terms of TLS fingerprinting like JA3. Does it alter the TLS settings at all like cipher suites & extensions? If it does, is there a way I can preserve the original TLS settings? Any info is appreciated, thank you! ### Describe alternatives you've considered _No response_ ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [X] Others

gitea-mirror closed this issue

2026-05-05 14:03:14 -06:00

gitea-mirror commented

2026-05-05 14:03:16 -06:00

Author

Owner

Copy link

@fatedier commented on GitHub (Feb 20, 2024):

We use the go standard library to handle TLS, without any extra logic.

@fatedier commented on GitHub (Feb 20, 2024): We use the go standard library to handle TLS, without any extra logic.

gitea-mirror commented

2026-05-05 14:03:17 -06:00

Author

Owner

Copy link

@dr3adx commented on GitHub (Feb 20, 2024):

We use the go standard library to handle TLS, without any extra logic.

so that means the TLS ja3 hash will be of golang library and not of the original request?

if so, is there a way to preserve original request's JA3? because right now everybody can detect we're using FRP based on ja3, correct me if im wrong.

@dr3adx commented on GitHub (Feb 20, 2024): > We use the go standard library to handle TLS, without any extra logic. so that means the TLS ja3 hash will be of golang library and not of the original request? if so, is there a way to preserve original request's JA3? because right now everybody can detect we're using FRP based on ja3, correct me if im wrong.

gitea-mirror commented

2026-05-05 14:03:17 -06:00

Author

Owner

Copy link

@fatedier commented on GitHub (Feb 20, 2024):

I do not understand this knowledge, you can try to obtain information in this area from other sources.

@fatedier commented on GitHub (Feb 20, 2024): I do not understand this knowledge, you can try to obtain information in this area from other sources.

No Branch/Tag specified