Add support for export_keying_material to SSL library
Open
Nobody has claimed this yet.
3.10
topic-SSL
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 37952 |
|---|---|
| Nosy | @wingel, @eighthave |
| PRs |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee = None
closed_at = None
created_at = <Date 2019-08-26.08:49:04.430>
labels = ['expert-SSL', 'type-feature', '3.10']
title = 'Add support for export_keying_material to SSL library'
updated_at = <Date 2022-03-20.14:18:50.161>
user = 'https://github.com/wingel'
bugs.python.org fields:
activity = <Date 2022-03-20.14:18:50.161>
actor = 'eighthave'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['SSL']
creation = <Date 2019-08-26.08:49:04.430>
creator = 'wingel71'
dependencies = []
files = []
hgrepos = []
issue_num = 37952
keywords = ['patch']
message_count = 9.0
messages = ['350512', '350513', '350514', '390433', '415553', '415569', '415579', '415585', '415604']
nosy_count = 2.0
nosy_names = ['wingel71', 'eighthave']
pr_nums = ['25255']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue37952'
versions = ['Python 3.10']
Contributor guide
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 by reviewing the SSL library context and the existing pull request python/cpython#25255, since the issue is in patch review and the pull request is named in the report. Compare that work with the requested export_keying_material support and confirm the relevant tests and completion criteria from the pull request discussion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 20/100