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
8261462: GCM ByteBuffer decryption problems #2487
Conversation
|
@ascarpino The following label will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command. |
Webrevs
|
Ping |
I will take a look. Thanks! |
Changes look good. Only nit is the copyright year of the 2 source files should be updated.
@ascarpino This change now passes all automated pre-integration checks. 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 715 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.
|
Wow.. I'm surprised those copyrights weren't changed. Thanks for the review |
/integrate |
@ascarpino Since your change was applied there have been 715 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit 414ee95. |
Hi,
I need a review of these two simple fixes. One just sets the input bytebuffer position to the limit upon completion of decryption. The second calls the CipherCore method to clear the state from the previous operation.
Thanks
Tony
Progress
Issue
Reviewers
Download
$ git fetch https://git.openjdk.java.net/jdk pull/2487/head:pull/2487
$ git checkout pull/2487