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
I am using TLS-Fuzzer to simulate a full TLS handshake with a pre-shared key (PSK) and would like to know if it's possible to configure a specific PSK value for the encrypted handshake messages.
Scenario:
Client: TLS-Fuzzer
Server: A dummy web server (acting as the TLS server)
In my specific use case, the key for encrypting the third message in the TLS 1.2 handshake (i.e., the Client Finished message) should be derived from the following parameters:
Client random number
Server random number
Pre-Shared Key (PSK)
Question:
How can I set a specific PSK value in TLS-Fuzzer to be used during the handshake process, particularly for generating the encryption key for the Client Finished message?
I have not been able to find documentation or examples on how to configure the PSK in the TLS-Fuzzer. Is there an existing way to:
Set a custom PSK for the handshake?
Ensure the PSK is used in conjunction with the Client and Server random values to generate the key for encryption?
Any guidance or examples would be greatly appreciated!
Discussion:
I am using TLS-Fuzzer to simulate a full TLS handshake with a pre-shared key (PSK) and would like to know if it's possible to configure a specific PSK value for the encrypted handshake messages.
Scenario:
In my specific use case, the key for encrypting the third message in the TLS 1.2 handshake (i.e., the Client Finished message) should be derived from the following parameters:
Question:
How can I set a specific PSK value in TLS-Fuzzer to be used during the handshake process, particularly for generating the encryption key for the Client Finished message?
I have not been able to find documentation or examples on how to configure the PSK in the TLS-Fuzzer. Is there an existing way to:
Any guidance or examples would be greatly appreciated!
Originally posted by @hamma96 in tlsfuzzer/tlsfuzzer#961
The text was updated successfully, but these errors were encountered: