Bug 1464896

Summary:	p11tool cannot generate DSA keys
Product:	Red Hat Enterprise Linux 7	Reporter:	Stanislav Zidek <szidek>
Component:	gnutls	Assignee:	Nikos Mavrogiannopoulos <nmavrogi>
Status:	CLOSED ERRATA	QA Contact:	Stanislav Zidek <szidek>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.4	CC:	aheverle, ansasaki, nmavrogi, szidek
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	gnutls-3.3.29-4.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-10-30 07:56:55 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1561481

Description Stanislav Zidek 2017-06-26 08:28:09 UTC

Description of problem:
p11tool cannot generate DSA keys

Version-Release number of selected component (if applicable):
gnutls-3.3.26-9.el7.x86_64
p11-kit-0.23.5-3.el7.x86_64
opensc-0.16.0-5.20170227git777e2a3.el7.x86_64
softhsm-2.1.0-2.el7.x86_64

How reproducible:


Steps to Reproduce:
1. softhsm2-util --init-token --free --label softhsm --pin 1234 --so-pin 1234
2. export GNUTLS_PIN=1234
3. p11tool -d 4 --batch --login --label testkey-dsa --outfile testkey-dsa.pub --generate-dsa '<token URL>'

Actual results:
Setting log level to 4
|<2>| p11: Initializing module: p11-kit-trust
|<2>| p11: Initializing module: opensc
|<2>| p11: Initializing module: softhsm
|<3>| ASSERT: pkcs11.c:665
|<2>| Initializing PKCS #11 modules
Token 'softhsm' with URL 'pkcs11:model=SoftHSM%20v2;manufacturer=SoftHSM%20project;serial=8c1126ee61dad5cd;token=softhsm' requires user PIN
|<2>| p11: Login result = 0
|<3>| ASSERT: pkcs11_privkey.c:879
|<2>| p11: Certain required fields are missing
Error in pkcs11_generate:651: PKCS #11 error.

Expected results:
... generation works

Additional info:
This is supposed to be already fixed in master.

Comment 10 errata-xmlrpc 2018-10-30 07:56:55 UTC

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-2018:3050