ssl.get_server_certificate should allow specifying certificate / key type
Open
Nobody has claimed this yet.
3.8 (EOL)
topic-SSL
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 31892 |
|---|---|
| Nosy | @tiran, @alex, @dstufft, @hannob |
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 2017-10-29.09:59:05.969>
labels = ['expert-SSL', 'type-feature', '3.8']
title = 'ssl.get_server_certificate should allow specifying certificate / key type'
updated_at = <Date 2022-03-15.13:21:55.154>
user = 'https://github.com/hannob'
bugs.python.org fields:
activity = <Date 2022-03-15.13:21:55.154>
actor = 'hanno'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['SSL']
creation = <Date 2017-10-29.09:59:05.969>
creator = 'hanno'
dependencies = []
files = []
hgrepos = []
issue_num = 31892
keywords = []
message_count = 5.0
messages = ['305182', '305380', '305414', '305420', '415242']
nosy_count = 5.0
nosy_names = ['janssen', 'christian.heimes', 'alex', 'dstufft', 'hanno']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue31892'
versions = ['Python 3.8']
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 at the ssl.get_server_certificate entry point and trace how it handles certificate and key types. Review the historical BPO discussion for the intended options; done means callers can specify the certificate/key type through this API.
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
- 35/100