Add getters for all SSLContext internal configuration

Open
#76,540 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
security

Research direction

Start by locating Python's SSLContext implementation and its existing tests, then review the SSL-specific issue context before deciding which internal configuration values need public getters. Done means the requested SSLContext configuration is exposed consistently and covered by tests, but the issue does not name specific files or values.

Written by the indexing model from the issue text.

Description

3.8 (EOL) topic-SSL type-feature
BPO 32359
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 2017-12-18.09:41:45.683>
labels = ['expert-SSL', 'type-feature', '3.8']
title = 'Add getters for all SSLContext internal configuration'
updated_at = <Date 2018-02-26.08:33:36.485>
user = 'https://github.com/njsmith'

bugs.python.org fields:

activity = <Date 2018-02-26.08:33:36.485>
actor = 'christian.heimes'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['SSL']
creation = <Date 2017-12-18.09:41:45.683>
creator = 'njs'
dependencies = []
files = []
hgrepos = []
issue_num = 32359
keywords = []
message_count = 8.0
messages = ['308533', '308535', '308536', '308541', '308547', '308548', '308594', '312890']
nosy_count = 5.0
nosy_names = ['janssen', 'christian.heimes', 'alex', 'njs', 'dstufft']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue32359'
versions = ['Python 3.8']

Dominant language
Python
Stars
77.2k
Forks
36k
Avg merge
1d 9h
Merged PRs (30d)
558

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from python/cpython

All issues in python/cpython

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.