Skip to content

fuzzer #537

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Odessasm opened this issue Dec 22, 2024 · 1 comment
Closed

fuzzer #537

Odessasm opened this issue Dec 22, 2024 · 1 comment
Labels
duplicate problem is better described in some other issue

Comments

@Odessasm
Copy link

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:

  • 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:

  1. Client random number
  2. Server random number
  3. 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:

  1. Set a custom PSK for the handshake?
  2. 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!

Originally posted by @hamma96 in tlsfuzzer/tlsfuzzer#961

@Odessasm Odessasm reopened this Dec 22, 2024
@tomato42
Copy link
Member

As I stated in tlsfuzzer/tlsfuzzer#961, the feature is not implemented in tlslite-ng: #22

there's a very rough implementation of it in #504, but I don't know when I'll be able to finish it.

@tomato42 tomato42 added the duplicate problem is better described in some other issue label Dec 30, 2024
@tomato42 tomato42 closed this as not planned Won't fix, can't repro, duplicate, stale Dec 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate problem is better described in some other issue
Projects
None yet
Development

No branches or pull requests

2 participants