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
Describe the solution you'd like
The server's JARM TLS fingerprint can be printed at the end of the Running client simulations via sockets section.
Not sure if any of the existing simulations can help in building the JARM TLS fingerprint or if all 10 additional simulations are needed.
In the Testing server defaults (Server Hello) section change "Fingerprints" to "Certificate Fingerprints" to avoid ambiguity.
The text was updated successfully, but these errors were encountered:
Similar as #2350 but the difference is that we need to calculate that on our own and there's a BSD clause in the published code which maybe an obstacle if somebody peeks at it and converts it to GPL'ed code. IANAL though
Which version are you referring to
3.2rc2 (default 3.1dev branch)
Describe your feature request (if it's a technical feature)
Report server's JARM TLS fingerprint.
https://github.com/salesforce/jarm
Describe the solution you'd like
The server's JARM TLS fingerprint can be printed at the end of the Running client simulations via sockets section.
Not sure if any of the existing simulations can help in building the JARM TLS fingerprint or if all 10 additional simulations are needed.
In the Testing server defaults (Server Hello) section change "Fingerprints" to "Certificate Fingerprints" to avoid ambiguity.
The text was updated successfully, but these errors were encountered: