-
Notifications
You must be signed in to change notification settings - Fork 208
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
8325254: CKA_TOKEN private and secret keys are not necessarily sensitive #2299
Conversation
👋 Welcome back fferrari! A progress list of the required criteria for merging this PR into |
@franferrax 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 56 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 (@martinuy) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
This backport pull request has now been updated with issue from the original commit. |
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.
Looks good to me.
/approval request 17u is affected by this bug because it has JDK-8271566 that introduced it. This is a second take of the previous (backed out) backport which addresses the missing P11Util::isNSS() issue. Better testing has been done to ensure the change does not introduce any regression, please see the "Testing" section in the pull request for further details. |
@franferrax |
/integrate |
@franferrax |
/sponsor |
Going to push as commit d29fe03.
Your commit was automatically rebased without conflicts. |
@martinuy @franferrax Pushed as commit d29fe03. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Hi, this is a second take of #2223, the backport of JDK-8325254: CKA_TOKEN private and secret keys are not necessarily sensitive, backed out by #2249.
Even though the original patch applies cleanly to 17u, it introduces a dependency on
P11Util::isNSS()
from JDK-8301553: Support Password-Based Cryptography in SunPKCS11.I only picked the
P11Util::isNSS()
changes since the whole PBE patch would require a deeper assessment and testing.Testing
linux-x86_64-server-release
andlinux-x86_64-server-slowdebug
test/jdk/sun/security/pkcs11
) in both buildsjdk:tier1
in both buildsbackport-8325254@franferrax/jdk17u-dev
Regards,
Francisco
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk17u-dev.git pull/2299/head:pull/2299
$ git checkout pull/2299
Update a local copy of the PR:
$ git checkout pull/2299
$ git pull https://git.openjdk.org/jdk17u-dev.git pull/2299/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 2299
View PR using the GUI difftool:
$ git pr show -t 2299
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk17u-dev/pull/2299.diff
Webrev
Link to Webrev Comment