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

Refactor extension verification #335

Open
tomato42 opened this issue Dec 20, 2018 · 0 comments
Open

Refactor extension verification #335

tomato42 opened this issue Dec 20, 2018 · 0 comments
Labels
complex Issues that require good knowledge of tlslite-ng internals or cryptography help wanted
Milestone
someday/future

Comments

@tomato42
Copy link
Member

currently extensions received from the other side are verified in multiple places, and likely multiple times

the code should be refactored to have verifiers for every extension type in one place and easy way to reuse them for tlsfuzzer.
@tomato42 tomato42 added help wanted complex Issues that require good knowledge of tlslite-ng internals or cryptography labels Dec 20, 2018
@tomato42 tomato42 added this to the someday/future milestone Dec 20, 2018
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 tlslite-ng internals or cryptography help wanted
Projects
None yet
Milestone
someday/future
Development

No branches or pull requests
1 participant
@tomato42