Add client authentication to tls.TLSSocket()
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 342
- Forks
- 82
- PR merge metrics
- No merged PRs in 30d
Description
The most complicated part of this is testing. We need to find a reliable way to test various scenarios including:
- Successful authentication
- Invalid authentication
- Weak certificate authentication?
Ideally we would use something like tls-o-matic.com, however they do not provide good and bad client certs to test with.
I have no interest in creating a VM for this since it will complicate testing.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the tls.TLSSocket() entry point and review how its current tests are organized. Investigate a reliable way to exercise successful, invalid, and possibly weak client-certificate authentication without a VM; done means those scenarios are covered by repeatable tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cryptography, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100