ssl docs say that ssl.SSLContext() is secure-by-default since 3.6, but it isn't
Open
Nobody has claimed this yet.
stdlib
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 38036 |
|---|---|
| Nosy | @tiran, @alex, @njsmith, @dstufft |
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-09-05.07:31:45.928>
labels = []
title = "ssl docs say that ssl.SSLContext() is secure-by-default since 3.6, but it isn't"
updated_at = <Date 2019-09-05.08:01:10.313>
user = 'https://github.com/njsmith'
bugs.python.org fields:
activity = <Date 2019-09-05.08:01:10.313>
actor = 'christian.heimes'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2019-09-05.07:31:45.928>
creator = 'njs'
dependencies = []
files = []
hgrepos = []
issue_num = 38036
keywords = []
message_count = 2.0
messages = ['351186', '351188']
nosy_count = 5.0
nosy_names = ['janssen', 'christian.heimes', 'alex', 'njs', 'dstufft']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue38036'
versions = []
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
Search the Python ssl documentation for the statement that ssl.SSLContext() is secure by default since Python 3.6, then compare it with the documented behavior. Update the inaccurate wording and verify that the resulting documentation accurately describes the default security configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100