-
Notifications
You must be signed in to change notification settings - Fork 30.5k
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.
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
buffer: don't compare same buffers #742
Conversation
This has potential information leak implications via timing attack. |
Don't think it does: the underlying implementation uses Also I don't see way for attacker to trigger this branch, as it requires to send the same buffer object somehow. |
@vkurchatkin LGTM but can you add one or two tests? |
@bnoordhuis just test comparing same objects? I couldn't imagine a failing test without reaching internals |
@vkurchatkin Just some regression tests in case someone horribly botches a merge and accidentally changes the |
7d551e0
to
fbcc74c
Compare
added some tests |
LGTM |
1 similar comment
LGTM |
PR-URL: #742 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Trevor Norris <trev.norris@gmail.com>
Landed in 1cd1d7a |
Copied from iojs: nodejs/node#742
Copied from iojs: nodejs/node#742
R=@trevnorris