You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is an method founded by the Salesforce engineers called "TLS fingerprinting" which can be used to found out the exact OS, browser, client data while making the TLS Handshake.
TODO:
found out how TLS fingerprint works
add implementation of it to the application
AC:
there is a rich comment with the exact information, articles and other resources about TLS fingerprint
there is an implementation of the whole thing
there is high test coverage in the newly written code
Comment:
I have been doing some research about the subject and in order to make it real and fully functional we need to somehow rewrite the server, in order to have access to all the data send in the TLS Handshake. Currently we have access to the method in the TLS config struct, which gives us access to the thing, but there aren't all the needed data about request in order to make it functional.
There are also already made implementation of the TLS Fingerprinting for the server side and client side in golang.
The text was updated successfully, but these errors were encountered:
Context:
There is an method founded by the Salesforce engineers called "TLS fingerprinting" which can be used to found out the exact OS, browser, client data while making the TLS Handshake.
TODO:
AC:
Comment:
I have been doing some research about the subject and in order to make it real and fully functional we need to somehow rewrite the server, in order to have access to all the data send in the TLS Handshake. Currently we have access to the method in the TLS config struct, which gives us access to the thing, but there aren't all the needed data about request in order to make it functional.
There are also already made implementation of the TLS Fingerprinting for the server side and client side in golang.
The text was updated successfully, but these errors were encountered: