Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 1374753 - p11-kit lacks pin-value support
p11-kit lacks pin-value support
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: p11-kit (Show other bugs)
7.4
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Daiki Ueno
Stanislav Zidek
:
Depends On:
Blocks: 1379283
  Show dependency tree / graph
 
Reported: 2016-09-09 10:11 EDT by David Woodhouse
Modified: 2017-08-01 12:52 EDT (History)
4 users (show)

See Also:
Fixed In Version: p11-kit-0.23.5-1.el7
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-08-01 12:52:09 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2017:1981 normal SHIPPED_LIVE p11-kit bug fix update 2017-08-01 13:58:17 EDT

  None (edit)
Description David Woodhouse 2016-09-09 10:11:44 EDT 
I'm doing test builds of openconnect on Centos7. I've had to disable the PKCS#11 testing because p11-kit lacks pin-value support so all the tests fail.

Please add support for the pin-value field.
Comment 8 errata-xmlrpc 2017-08-01 12:52:09 EDT 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2017:1981
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.