RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
While listing or deleting objects on PKCS#11 token, p11tool fails to consume pin from URI.

This is regression against RHEL-7, but definitely not a blocker.

Version-Release number of selected component (if applicable):
# rpm -q gnutls p11-kit softhsm
gnutls-3.6.5-2.el8.x86_64
p11-kit-0.23.14-4.el8.x86_64
softhsm-2.4.0-1.el8.x86_64

RHEL-8.0.0-20190228.1

How reproducible:
always

Steps to Reproduce:
1. setup softhsm token and generate private key in it
2. p11tool --batch --login --list-all-privkeys '$token?pin-value=$PIN'


Actual results:
Object 0:
	URL: pkcs11:model=SoftHSM%20v2;manufacturer=SoftHSM%20project;serial=732c1c70bd195b7b;token=softhsm;id=%b8%9a%a7%5e%9a%59%eb%d9%de%e2%3d%97%28%e5%8f%c4%54%ac%6a%71;object=testkey-rsa;type=private
No PIN given.
note: when operating in batch mode, set the GNUTLS_PIN or GNUTLS_SO_PIN environment variables


Expected results:
... listed normally

Additional info:
Interestingly enough, pin-value specification works with --generate-* operations.

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/RHSA-2019:3600