tlsfuzzer/tlslite-ng

Refactor extension verification

Open

#335 opened on Dec 20, 2018

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Python (95 forks)auto 404
complexhelp wanted

Repository metrics

Stars
 (269 stars)
PR merge metrics
 (PR metrics pending)

Description

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.

Contributor guide

Research direction
Identify all places in the codebase where extension verification occurs, then create a unified verifier for each extension type and ensure reuse for tlsfuzzer.
Tech stack
python
Domain
backendnetworkingsecurity
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
PythonTLS basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60