python / python/cpython

SSL_shutdown needs SSL_read() until SSL_ERROR_ZERO_RETURN

Open
#74,622 8 comments 0 reactions 1 assignee View on GitHub

@tiran is already working on this.

Since May 23, 2017.

3.7 (EOL) 3.8 (EOL) topic-SSL
Dominant language
Python
Stars
77.2k
Forks
36k
PR merge metrics
PR metrics pending

Description

BPO 30437
Nosy @tiran, @alex, @njsmith, @vadmium, @dstufft
PRs
  • python/cpython#6977
  • 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 = 'https://github.com/tiran'
    closed_at = None
    created_at = <Date 2017-05-23.03:44:13.123>
    labels = ['expert-SSL', '3.7', '3.8']
    title = 'SSL_shutdown needs SSL_read() until SSL_ERROR_ZERO_RETURN'
    updated_at = <Date 2018-05-23.13:55:30.894>
    user = 'https://github.com/njsmith'
    

    bugs.python.org fields:

    activity = <Date 2018-05-23.13:55:30.894>
    actor = 'christian.heimes'
    assignee = 'christian.heimes'
    closed = False
    closed_date = None
    closer = None
    components = ['SSL']
    creation = <Date 2017-05-23.03:44:13.123>
    creator = 'njs'
    dependencies = []
    files = []
    hgrepos = []
    issue_num = 30437
    keywords = ['patch']
    message_count = 8.0
    messages = ['294216', '294245', '294299', '294301', '301472', '301491', '317028', '317407']
    nosy_count = 6.0
    nosy_names = ['janssen', 'christian.heimes', 'alex', 'njs', 'martin.panter', 'dstufft']
    pr_nums = ['6977']
    priority = 'high'
    resolution = None
    stage = 'patch review'
    status = 'open'
    superseder = None
    type = None
    url = 'https://bugs.python.org/issue30437'
    versions = ['Python 2.7', 'Python 3.6', 'Python 3.7', 'Python 3.8']
    

    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.

    Assessment

    This issue has not been assessed yet.

    Get new issues in your inbox

    A short digest of beginner-friendly GitHub issues.