Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Timing based static (EC)DH key recovery #681

Open
tomato42 opened this issue Jul 16, 2020 · 0 comments
Open

Timing based static (EC)DH key recovery #681

tomato42 opened this issue Jul 16, 2020 · 0 comments
Labels
complex Issues that require good knowledge of tlsfuzzer internals enhancement new feature to be implemented help wanted new test script will require creation of a new connection script
Projects
Vulnerability testers

Comments

@tomato42
Copy link
Member

While most servers use an ECDH or FFDH key just once, some protocols, like ETS (formerly known as eTLS) suggest that servers should use a static DH key share.

We should add a test to see if the timing of server responses doesn't depend on client key shares.
@tomato42 tomato42 added enhancement new feature to be implemented help wanted new test script will require creation of a new connection script complex Issues that require good knowledge of tlsfuzzer internals labels Jul 16, 2020
@tomato42 tomato42 added this to To do in Vulnerability testers via automation Jul 16, 2020
@tomato42 tomato42 changed the title Timing based (EC)DH key recovery Timing based static (EC)DH key recovery Jul 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
complex Issues that require good knowledge of tlsfuzzer internals enhancement new feature to be implemented help wanted new test script will require creation of a new connection script
Projects
Vulnerability testers
  
To do
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tomato42