-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8294906: Memory leak in PKCS11 NSS TLS server #10594
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
|
👋 Welcome back djelinski! A progress list of the required criteria for merging this PR into |
|
@djelinski 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
|
|
I will take a look, thanks~ |
|
Would this fix cause problems for non-NSS providers when trying to destroy a mac key that was never allocated? Or does |
|
I don't know if other providers allocate mac keys here or not; NSS is the only provider I could test. The spec says:
which suggests that the keys may be absent; it does not define how we can check if keys were generated, but it does declare that zero ( |
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 fine, just have one nit.
Thanks for finding and fixing this!
|
BTW, if this NSS behavior is still present in newer NSS releases, we should raise the priority of this and backport it. |
|
@djelinski 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 92 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 |
|
Thanks for the review! Comment added. I was unable to find any working Windows NSS binaries that are less than 3 years old; apparently there are no official builds. I tried using Firefox's NSS, but for some reason Java couldn't load them. |
|
On Linux you might be able to use brew to get an older version of nss: |
|
Verified that the behavior is still present in NSS 3.82. JBS updated. /integrate |
|
Going to push as commit 94caecb.
Your commit was automatically rebased without conflicts. |
|
@djelinski Pushed as commit 94caecb. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
C_DeriveKey with mechanisms
CKM_*_KEY_AND_MAC_DERIVEalways returns mac keys, even if macBits is zero. These keys must be free'd when no longer needed.Verified that:
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/10594/head:pull/10594$ git checkout pull/10594Update a local copy of the PR:
$ git checkout pull/10594$ git pull https://git.openjdk.org/jdk pull/10594/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 10594View PR using the GUI difftool:
$ git pr show -t 10594Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/10594.diff