Red Hat Bugzilla – Bug 1375463
doc update: certtool's manpage does not mention it cannot handle PKCS#11 URLs for certain options
Last modified: 2017-08-01 04:48:22 EDT
Description of problem: Some options of certtool should accept PKCS#11 URLs according to man page (e.g., --load-ca-certificate). Version-Release number of selected component (if applicable): gnutls-3.3.24-1.el7 How reproducible: always Steps to Reproduce: 1. export GNUTLS_PIN=1234; export GNUTLS_SO_PIN=1234 2. softhsm2-util --init-token --free --label softhsm --pin $GNUTLS_PIN --so-pin $GNUTLS_SO_PIN 3. p11tool --so-login --batch --label '$CA_LABEL' --mark-trusted --mark-ca --load-certificate <<CA cert>> --write '<<TOKEN>>' 4. certtool --verify --provider /usr/lib64/pkcs11/libsofthsm2.so --load-ca-certificate '<<CA cert PKCS11 URL>>' <cert.pem (signed by CA) Actual results: Could not open <<CA cert PKCS11 URL>> Expected results: Certificate verified. Additional info: Problem is same with system and default trust store when accessed through PKCS11 URLs.
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-2017:2292