[SSL: BAD_WRITE_RETRY] bad write retry in _ssl.c:1636

Open
#66,689 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
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
c, python
Domain
networking, security

Research direction

Start by inspecting _ssl.c around line 1636 and the original BPO issue 22499 to recover the failure scenario. The payload names no test or reproduction, so completion requires identifying the bad write-retry behavior, adding regression coverage, and confirming the SSL test suite passes.

Written by the indexing model from the issue text.

Description

stdlib type-bug
BPO 22499
Nosy @pitrou, @giampaolo, @tiran, @alex, @skrah, @dstufft, @GLolol, @xgid

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-26.01:24:30.426>
labels = ['type-bug', 'library']
title = '[SSL: BAD_WRITE_RETRY] bad write retry in _ssl.c:1636'
updated_at = <Date 2018-09-23.17:16:46.563>
user = 'https://bugs.python.org/nikratio'

bugs.python.org fields:

activity = <Date 2018-09-23.17:16:46.563>
actor = 'tacocat'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2014-09-26.01:24:30.426>
creator = 'nikratio'
dependencies = []
files = []
hgrepos = []
issue_num = 22499
keywords = []
message_count = 9.0
messages = ['227582', '227583', '254343', '254389', '257350', '257413', '257535', '257562', '257614']
nosy_count = 10.0
nosy_names = ['janssen', 'pitrou', 'giampaolo.rodola', 'christian.heimes', 'alex', 'nikratio', 'skrah', 'dstufft', 'tacocat', 'xgdomingo']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue22499'
versions = ['Python 3.4', 'Python 3.5']

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.