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

Test coverage for compress_certificate extension (RFC8879) #923

Open
tomato42 opened this issue Apr 15, 2024 · 0 comments
Open

Test coverage for compress_certificate extension (RFC8879) #923

tomato42 opened this issue Apr 15, 2024 · 0 comments
Labels
complex Issues that require good knowledge of tlsfuzzer internals enhancement new feature to be implemented new test script will require creation of a new connection script
Projects
TLS extensions

Comments

@tomato42
Copy link
Member

tomato42 commented Apr 15, 2024 •
edited

Feature request

Is your feature request related to a problem? Please describe

The tlsfuzzer should support the TLS Certificate Compression RFC8879 extension.
It should include test coverage for the extension.

Describe the solution you'd like

Extension supported, test coverage present, executed and verified against OpenSSL (3.2.0 includes support), maybe others.

Describe alternatives you've considered

There are no real alternatives

Additional context

Required: tlsfuzzer/tlslite-ng#431
@tomato42 tomato42 added enhancement new feature to be implemented new test script will require creation of a new connection script complex Issues that require good knowledge of tlsfuzzer internals labels Apr 15, 2024
@tomato42 tomato42 added this to To do in TLS extensions via automation Apr 15, 2024
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 new test script will require creation of a new connection script
Projects
TLS extensions
  
To do
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tomato42