-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8281628: KeyAgreement : generateSecret intermittently not resetting #7665
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
Conversation
8281628: KeyAgreement : generateSecret intermittently not resetting
|
👋 Welcome back weijun! A progress list of the required criteria for merging this PR into |
Webrevs
|
| } else { | ||
| // Array too short, pad it w/ leading 0s | ||
| if (secret.length < expectedLen) { | ||
| Arrays.fill(sharedSecret, offset, offset + (expectedLen - secret.length), (byte)0); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: longer than 80 chars?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll wrap it.
| * @test | ||
| * @bug 8281628 | ||
| * @library /test/lib | ||
| * @summary KeyAgreement : generateSecret intermittently not resetting |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: describe the fix instead of just using the bug synopsis.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK.
| aliceSecret[0] = 0; | ||
| bobSecret[0] = 1; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Instead of only the first byte difference, would it be easier to trigger the bug with completely different buffer value, say FFFFFF vs 000000?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe not. When the generated secret is shorter, the padded bytes are always at the beginning.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With a bigger buffer, i.e. say 80-byte long, instead of 64-byte, I'd expect a difference and higher reproducibility...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After n = generateSecret(secret, offset) is called, only n bytes from offset should be touched, and in this case n is 64. Even if you allocate 80 bytes of data, we should not compare those after the 64th byte.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But you remind me I should not take it for granted that the return value is always 64 and it should be checked as well. A new commit pushed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, I see, I confused the actual length with the buffer length. In the case where the generated bytes are shorter, the difference is only one byte, so setting other bytes do not matter.
valeriepeng
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes look good.
|
@wangweij This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be: You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 34 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. ➡️ To integrate this PR with the above commit message to the |
|
/integrate |
|
Going to push as commit 1485883.
Your commit was automatically rebased without conflicts. |
The comment said "pad it w/ leading 0s". So let's pad it.
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/7665/head:pull/7665$ git checkout pull/7665Update a local copy of the PR:
$ git checkout pull/7665$ git pull https://git.openjdk.java.net/jdk pull/7665/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 7665View PR using the GUI difftool:
$ git pr show -t 7665Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/7665.diff