Loading...

XML

Word

Printable

Type: Bug
Resolution: Fixed
Priority: P5
Fix Version/s: 11
Affects Version/s: 10.0.1
Component/s: security-libs
Labels:
- autoverify
- noreg-hard

Subcomponent:
javax.crypto:pkcs11
Resolved In Build:
b17
CPU:

generic
OS:

generic
Verification:
Not verified

Issue	Fix Version	Assignee	Priority	Status	Resolution	Resolved In Build
JDK-8204755	11.0.1	Martin Balao Alonso	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 Alonso	P5	Closed	Duplicate
JDK-8204484	openjdk7u	Martin Balao Alonso	P5	Resolved	Fixed	master

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

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)

Assignee:: Valerie Peng

Reporter:: Martin Balao Alonso

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Created:: 2018-05-14 14:36

Updated:: 2019-01-13 22:42

Resolved:: 2018-06-01 12:52

Details

Backports

Description

Attachments

Issue Links

Activity

People

Dates