Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[v10.x] tls: renegotiate should take care of its own state #27938

Closed
wants to merge 1 commit into from
Closed

[v10.x] tls: renegotiate should take care of its own state #27938

wants to merge 1 commit into from

Commits on May 28, 2019

  1. tls: renegotiate should take care of its own state 

    In the initial version of this test there were two zero-length writes to
force tls state to cycle. The second is not necessary, at least not now,
but the first was. The renegotiate() API should ensure that packet
exchange takes place, not its users, so move the zero-length write into
tls.

See: nodejs#14239
See: nodejs@b1909d3a70f9

PR-URL: nodejs#25997
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
    @sam-github @MylesBorins
    sam-github authored and MylesBorins committed May 28, 2019
    Configuration menu
    Copy the full SHA
    fa4470f View commit details
    Browse the repository at this point in the history