Skip to content

8271566: DSA signature length value is not accurate in P11Signature#3166

Open
zzambers wants to merge 1 commit intoopenjdk:masterfrom
zzambers:dsa-signature-length-standalone
Open

8271566: DSA signature length value is not accurate in P11Signature#3166
zzambers wants to merge 1 commit intoopenjdk:masterfrom
zzambers:dsa-signature-length-standalone

Conversation

@zzambers
Copy link
Copy Markdown
Contributor

@zzambers zzambers commented Mar 4, 2026

Backport to fix failure we are seeing in some of our tests for jdk11 in FIPS mode (using sunpkcs11 provider):

java.security.ProviderException: cancel failed
	at jdk.crypto.cryptoki/sun.security.pkcs11.P11Signature.cancelOperation(P11Signature.java:332)
	at jdk.crypto.cryptoki/sun.security.pkcs11.P11Signature.reset(P11Signature.java:272)
	at jdk.crypto.cryptoki/sun.security.pkcs11.P11Signature.engineVerify(P11Signature.java:755)
	at java.base/java.security.Signature$Delegate.engineVerify(Signature.java:1416)
	at java.base/java.security.Signature.verify(Signature.java:790)
...
Caused by: sun.security.pkcs11.wrapper.PKCS11Exception: CKR_ARGUMENTS_BAD
	at jdk.crypto.cryptoki/sun.security.pkcs11.wrapper.PKCS11.C_VerifyFinal(Native Method)
	at jdk.crypto.cryptoki/sun.security.pkcs11.P11Signature.cancelOperation(P11Signature.java:305)
	... 14 more

Backport only affects PKCS11 provider. Not clean because JDK-8242332 (missing in jdk11), made small changes (in-between) to engineSign and cancelOperation methods in P11Signature class in regards to DSA, which were then completely overwritten by this change set (so not an actual dependency).

Testing:
Fixes issue higher.
GHA: OK
pkcs11 tests (test/jdk/sun/security/pkcs11): OK
ssl-tests with TEST_PKCS11_FIPS=1: OK


Progress

  • Change must be properly reviewed (1 review required, with at least 1 Reviewer)
  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue
  • JDK-8271566 needs maintainer approval

Issue

  • JDK-8271566: DSA signature length value is not accurate in P11Signature (Bug - P4)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk11u-dev.git pull/3166/head:pull/3166
$ git checkout pull/3166

Update a local copy of the PR:
$ git checkout pull/3166
$ git pull https://git.openjdk.org/jdk11u-dev.git pull/3166/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 3166

View PR using the GUI difftool:
$ git pr show -t 3166

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk11u-dev/pull/3166.diff

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link
Copy Markdown

bridgekeeper Bot commented Mar 4, 2026

👋 Welcome back zzambers! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

@openjdk
Copy link
Copy Markdown

openjdk Bot commented Mar 4, 2026

❗ This change is not yet ready to be integrated.
See the Progress checklist in the description for automated requirements.

@openjdk openjdk Bot changed the title Backport 9165f777f86fd333d4c17702b7e6289bfdbb5e1e 8271566: DSA signature length value is not accurate in P11Signature Mar 4, 2026
@openjdk
Copy link
Copy Markdown

openjdk Bot commented Mar 4, 2026

This backport pull request has now been updated with issue from the original commit.

@openjdk openjdk Bot added backport Port of a pull request already in a different code base rfr Pull request is ready for review labels Mar 4, 2026
@mlbridge
Copy link
Copy Markdown

mlbridge Bot commented Mar 4, 2026

Webrevs

@gnu-andrew
Copy link
Copy Markdown
Member

I seem to remember there were reasons for not backporting this before. Given the follow-on issues, it should certainly wait until we start the July cycle next week.

@franferrax can you give your take on the risk of this one? Thanks.

@bridgekeeper
Copy link
Copy Markdown

bridgekeeper Bot commented Apr 3, 2026

@zzambers This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply issue a /touch or /keepalive command to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration!

@zzambers
Copy link
Copy Markdown
Contributor Author

zzambers commented Apr 7, 2026

/touch

@openjdk
Copy link
Copy Markdown

openjdk Bot commented Apr 7, 2026

@zzambers The pull request is being re-evaluated and the inactivity timeout has been reset.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport Port of a pull request already in a different code base rfr Pull request is ready for review

Development

Successfully merging this pull request may close these issues.

2 participants