Skip to content

Conversation

@indutny
Copy link
Member

Do not attempt to read data from the socket whilst on OpenSSL's stack,
weird things may happen, and this is most likely going to result in some
kind of error.

R=@trevnorris

Let's land this change anyway, so it will be easier to work on our AsyncWrap stuff.

Not really going to introduce a test here, because this thing will fail once #4509 or any similar PR will land.

Do not attempt to read data from the socket whilst on OpenSSL's stack, weird things may happen, and this is most likely going to result in some kind of error.
@trevnorris
Copy link
Contributor

Awesome. LGTM.

@trevnorristrevnorris added the tls Issues and PRs related to the tls subsystem. label Jan 11, 2016
@indutny
Copy link
MemberAuthor

@jasnell
Copy link
Member

LGTM

@indutny
Copy link
MemberAuthor

cc @nodejs/crypto just in case

@indutny
Copy link
MemberAuthor

Landed in 5a2445b, thank you everyone!

@indutnyindutny closed this Jan 11, 2016
indutny added a commit that referenced this pull request Jan 11, 2016
Do not attempt to read data from the socket whilst on OpenSSL's stack, weird things may happen, and this is most likely going to result in some kind of error. PR-URL: #4624 Reviewed-By: Trevor Norris <[email protected]> Reviewed-By: James M Snell <[email protected]>
@indutnyindutny deleted the land/gist-70b5 branch January 11, 2016 20:11
@MylesBorins
Copy link
Contributor

@indutny should this be rolled into v5.4.1 or should we wait for @nodejs/crypto to take a look?

@indutny
Copy link
MemberAuthor

It should be safe to roll it into v5.4.1

MylesBorins pushed a commit that referenced this pull request Jan 12, 2016
Do not attempt to read data from the socket whilst on OpenSSL's stack, weird things may happen, and this is most likely going to result in some kind of error. PR-URL: #4624 Reviewed-By: Trevor Norris <[email protected]> Reviewed-By: James M Snell <[email protected]>
@MylesBorinsMylesBorins mentioned this pull request Jan 12, 2016
MylesBorins pushed a commit that referenced this pull request Jan 28, 2016
Do not attempt to read data from the socket whilst on OpenSSL's stack, weird things may happen, and this is most likely going to result in some kind of error. PR-URL: #4624 Reviewed-By: Trevor Norris <[email protected]> Reviewed-By: James M Snell <[email protected]>
MylesBorins pushed a commit that referenced this pull request Feb 11, 2016
Do not attempt to read data from the socket whilst on OpenSSL's stack, weird things may happen, and this is most likely going to result in some kind of error. PR-URL: #4624 Reviewed-By: Trevor Norris <[email protected]> Reviewed-By: James M Snell <[email protected]>
MylesBorins pushed a commit to MylesBorins/node that referenced this pull request Feb 11, 2016
Do not attempt to read data from the socket whilst on OpenSSL's stack, weird things may happen, and this is most likely going to result in some kind of error. PR-URL: nodejs#4624 Reviewed-By: Trevor Norris <[email protected]> Reviewed-By: James M Snell <[email protected]>
@MylesBorinsMylesBorins mentioned this pull request Feb 11, 2016
MylesBorins pushed a commit to MylesBorins/node that referenced this pull request Feb 15, 2016
Do not attempt to read data from the socket whilst on OpenSSL's stack, weird things may happen, and this is most likely going to result in some kind of error. PR-URL: nodejs#4624 Reviewed-By: Trevor Norris <[email protected]> Reviewed-By: James M Snell <[email protected]>
scovetta pushed a commit to scovetta/node that referenced this pull request Apr 2, 2016
Do not attempt to read data from the socket whilst on OpenSSL's stack, weird things may happen, and this is most likely going to result in some kind of error. PR-URL: nodejs#4624 Reviewed-By: Trevor Norris <[email protected]> Reviewed-By: James M Snell <[email protected]>
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

tlsIssues and PRs related to the tls subsystem.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

@indutny@trevnorris@jasnell@MylesBorins