-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P4
-
Affects Version/s: 26
-
Component/s: security-libs
-
b22
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8372257 | 25.0.3-oracle | Govindan Srinivassan | P4 | Resolved | Fixed | master |
| JDK-8372314 | 21.0.11-oracle | Govindan Srinivassan | P4 | Resolved | Fixed | master |
| JDK-8372315 | 17.0.19-oracle | Govindan Srinivassan | P4 | Resolved | Fixed | master |
| JDK-8372391 | 11.0.31-oracle | Govindan Srinivassan | P4 | Resolved | Fixed | master |
The following tests use PKCS11Test.isBadNSSVersion() to determine if they should be skipped.
- TestCurves
- TestECDH2
- TestECDSA
- TestECDSA2
- TestECGenSpec
The `isBadNSSVersion()` method converts the version number to a double and checks if the version is greater than 3.11 but less than 3.12. The current NSS version number is 3.111 which causes the test to be skipped.
Update the logic to correctly handle major/minor version numbers. However, because NSS is so far beyond 3.11 and 3.12, can we just remove the method entirely?
- TestCurves
- TestECDH2
- TestECDSA
- TestECDSA2
- TestECGenSpec
The `isBadNSSVersion()` method converts the version number to a double and checks if the version is greater than 3.11 but less than 3.12. The current NSS version number is 3.111 which causes the test to be skipped.
Update the logic to correctly handle major/minor version numbers. However, because NSS is so far beyond 3.11 and 3.12, can we just remove the method entirely?
- backported by
-
JDK-8372257 Some PKCS11Tests are being skipped when they shouldn't
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
- links to
-
Commit(master)
openjdk/jdk/cc9483b4
-
Review(master)
openjdk/jdk25u-dev/59
-
Review(master)
openjdk/jdk/27095
(2 links to)