SSLContext.load_verify_locations(cadata) does not accept CRLs

Open
#66,561 3 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
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
security

Research direction

Start at the SSLContext.load_verify_locations(cadata) entry point and review how cadata is currently handled for certificate verification. Confirm the expected CRL input format and add coverage showing that CRLs are accepted, with completion indicated by the relevant SSL behavior working without rejection.

Written by the indexing model from the issue text.

Description

3.8 (EOL) topic-SSL type-bug
BPO 22365
Nosy @pitrou, @giampaolo, @tiran, @alex, @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 2014-09-08.14:54:46.733>
labels = ['expert-SSL', 'type-bug', '3.8']
title = 'SSLContext.load_verify_locations(cadata) does not accept CRLs'
updated_at = <Date 2018-02-26.08:28:49.140>
user = 'https://bugs.python.org/RalphBroenink'

bugs.python.org fields:

activity = <Date 2018-02-26.08:28:49.140>
actor = 'christian.heimes'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['SSL']
creation = <Date 2014-09-08.14:54:46.733>
creator = 'Ralph.Broenink'
dependencies = []
files = []
hgrepos = []
issue_num = 22365
keywords = []
message_count = 3.0
messages = ['226582', '226626', '301514']
nosy_count = 7.0
nosy_names = ['janssen', 'pitrou', 'giampaolo.rodola', 'christian.heimes', 'alex', 'dstufft', 'Ralph.Broenink']
pr_nums = []
priority = 'low'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue22365'
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.