-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
4964430: (spec) missing IllegalStateException exception requirement for javax.crypto.Cipher.doFinal #15727
Conversation
👋 Welcome back blperez01! A progress list of the required criteria for merging this PR into |
@blperez01 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
|
|
The current documentation for Cipher.updateAAD(...) is: "@throws IllegalStateException if this {@code Cipher} object is in a wrong state (e.g., has not been initialized), does not accept AAD, or if operating in either GCM or CCM mode and one of the {@code update} methods has already been called for the active encryption/decryption operation" This seems fairly explicit, but I could change the wording to "@throws IllegalStateException if this {@code Cipher} object is in a wrong state (e.g., has not been initialized, or is not in ENCRYPT_MODE or DECRYPT_MODE)" |
We still need the part of "does not accept AAD, or if operating in either GCM or CCM mode and one of the {@code update} methods has already been called for the active encryption/decryption operation". |
Current documentation is: "The {@code NullCipher} class is a class that provides an "identity cipher" -- one that does not transform the plain text. As a consequence, the ciphertext is identical to the plaintext. All initialization methods do nothing, while the blocksize is set to 1 byte." Would it be sufficient for me to add "Unlike other ciphers, the {@code NullCipher} will not throw an {@code IllegalStateException} when calling {@code Cipher} methods in an incorrect state." |
…StateException when calling Cipher methods in bad state
@@ -1851,7 +1851,8 @@ private void checkCipherState() { | |||
* new block | |||
* | |||
* @throws IllegalStateException if this {@code Cipher} object is in a | |||
* wrong state (e.g., has not been initialized) | |||
* wrong state (e.g., has not been initialized, or is not | |||
* in ENCRYPT_MODE or DECRYPT_MODE) |
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.
Use code format when referencing the modes, ex: change this line to:
* in {@code ENCRYPT_MODE} or {@code DECRYPT_MODE})
Same comment applies to all other applicable lines below.
* {@code IllegalStateException} when calling {@code Cipher} methods | ||
* in an incorrect state. |
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.
Suggest rewording last part as "... when {@code Cipher} methods are called in an incorrect state." I also think we should say a NullCipher has no state. So how about:
"Unlike other ciphers, the {@code NullCipher} has no state, and will not throw an {@code IllegalStateException} when {@code Cipher} methods are called in an incorrect state."
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.
Well, if it has no state it cannot be in an incorrect state so the " in an incorrect state" part can be omitted.
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.
Good point!
@blperez01 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 591 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. As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@seanjmullan, @valeriepeng) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
/integrate |
@blperez01 |
/sponsor |
Going to push as commit 991ce84.
Your commit was automatically rebased without conflicts. |
@valeriepeng @blperez01 Pushed as commit 991ce84. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Updated IllegalStateException exception requirements for
update
,doFinal
,wrap
, andunwrap
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/15727/head:pull/15727
$ git checkout pull/15727
Update a local copy of the PR:
$ git checkout pull/15727
$ git pull https://git.openjdk.org/jdk.git pull/15727/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 15727
View PR using the GUI difftool:
$ git pr show -t 15727
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/15727.diff
Webrev
Link to Webrev Comment