Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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:
"p11-kit" doesn't print the "extract" option but manual contains it. RHEL-6 version prints this kind of information.
Version-Release number of selected component (if applicable):
p11-kit-0.20.7-2.el7
How reproducible:
Always
Steps to Reproduce:
1. zcat $(rpm -ql p11-kit | grep 'man' | grep '/p11-kit.') | grep 'extract' && { printf "\n======\n\n"; p11-kit --help 2>&1 | grep 'extract' && printf "\nPASS\n" || printf "\nFAIL\n"; } || echo 'PASS - no manual also'
Actual results:
.HP \w'\fBp11\-kit\ extract\fR\ 'u
\fBp11\-kit extract\fR \&.\&.\&.
======
FAIL
Expected results:
.HP \w'\fBp11\-kit\ extract\fR\ 'u
\fBp11\-kit extract\fR \-\-filter=<what> \-\-format=<type> /path/to/destination
$ p11\-kit extract \-\-format=x509\-directory \-\-filter=ca\-anchors /path/to/directory
You can specify the following options to control what to extract\&. The
Specifies what certificates to extract\&. You can specify the following values:
None of the available formats support storage of blacklist entries that do not contain a full certificate\&. Thus any certificates blacklisted by their issuer and serial number alone, are not included in the extracted blacklist\&.
$ p11\-kit extract\-trust
OpenSSL, GnuTLS and Java cannot currently read trust information directly from the trust policy module\&. This command extracts trust information such as certificate anchors for use by these libraries\&.
What this command does, and where it extracts the files is distribution or site specific\&. Packagers or administrators are expected customize this command\&.
======
extract Extract certificates
PASS
Additional info:
"p11-kit" utility has been refactored to "trust" utility in RHEL-7.1 but still "p11-kit" is present and allows this functionality.
This command has been moved to 'trust extract', it continues to work in its older 'p11-kit extract' form, however it is not listed in the help output.
The 'man p11-kit' command refers you to the 'man trust' manual page.
I believe this is all in order.
Comment 4RHEL Program Management
2014-11-11 11:05:46 UTC
Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.
Yes, the bug report is still valid although I find it really low priority.
Current man page does not clearly state how to use the "p11-kit extract ..." command. It seems that both "p11-kit extract ..." and "trust extract ..." forms could be used but according to #c7 the user should rather use the trust command.
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
Description of problem: "p11-kit" doesn't print the "extract" option but manual contains it. RHEL-6 version prints this kind of information. Version-Release number of selected component (if applicable): p11-kit-0.20.7-2.el7 How reproducible: Always Steps to Reproduce: 1. zcat $(rpm -ql p11-kit | grep 'man' | grep '/p11-kit.') | grep 'extract' && { printf "\n======\n\n"; p11-kit --help 2>&1 | grep 'extract' && printf "\nPASS\n" || printf "\nFAIL\n"; } || echo 'PASS - no manual also' Actual results: .HP \w'\fBp11\-kit\ extract\fR\ 'u \fBp11\-kit extract\fR \&.\&.\&. ====== FAIL Expected results: .HP \w'\fBp11\-kit\ extract\fR\ 'u \fBp11\-kit extract\fR \-\-filter=<what> \-\-format=<type> /path/to/destination $ p11\-kit extract \-\-format=x509\-directory \-\-filter=ca\-anchors /path/to/directory You can specify the following options to control what to extract\&. The Specifies what certificates to extract\&. You can specify the following values: None of the available formats support storage of blacklist entries that do not contain a full certificate\&. Thus any certificates blacklisted by their issuer and serial number alone, are not included in the extracted blacklist\&. $ p11\-kit extract\-trust OpenSSL, GnuTLS and Java cannot currently read trust information directly from the trust policy module\&. This command extracts trust information such as certificate anchors for use by these libraries\&. What this command does, and where it extracts the files is distribution or site specific\&. Packagers or administrators are expected customize this command\&. ====== extract Extract certificates PASS Additional info: "p11-kit" utility has been refactored to "trust" utility in RHEL-7.1 but still "p11-kit" is present and allows this functionality.