Details
-
Bug
-
Status: Closed
-
P5
-
Resolution: Fixed
-
10.0.1
-
b17
-
generic
-
generic
-
Not verified
Backports
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8204755 | 11.0.1 | Martin Balao | P5 | Resolved | Fixed | team |
JDK-8208975 | 8u201 | Ivan Gerasimov | P5 | Resolved | Fixed | b01 |
JDK-8204343 | 8u192 | Ivan Gerasimov | P5 | Resolved | Fixed | b01 |
JDK-8216877 | emb-8u201 | Ivan Gerasimov | P5 | Resolved | Fixed | master |
JDK-8204344 | 7u191 | Martin Balao | P5 | Closed | Duplicate | |
JDK-8204484 | openjdk7u | Martin Balao | P5 | Resolved | Fixed | master |
Description
If initializing a SunPKCS11 Signature fails because C_SignInit or C_VerifyInit functions throw a PKCS11Exception exception, allocated session is not released. If this happens multiple times, token resources may be exhausted leading to an error. It's suggested to implement the same idiom as for SunPKCS11 Cipher objects. That is: release the session if initialization fails.
Bug originally reported by: Hemant B Khot
Bug originally reported by: Hemant B Khot
Attachments
Issue Links
- backported by
-
JDK-8204343 Release session if initialization of SunPKCS11 Signature fails
-
- Resolved
-
-
JDK-8204484 Release session if initialization of SunPKCS11 Signature fails
-
- Resolved
-
-
JDK-8204755 Release session if initialization of SunPKCS11 Signature fails
-
- Resolved
-
-
JDK-8208975 Release session if initialization of SunPKCS11 Signature fails
-
- Resolved
-
-
JDK-8216877 Release session if initialization of SunPKCS11 Signature fails
-
- Resolved
-
-
JDK-8204344 Release session if initialization of SunPKCS11 Signature fails
-
- Closed
-
(1 backported by)