Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1160783 - p11-kit miss the extract option in help
p11-kit miss the extract option in help
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: p11-kit (Show other bugs)
7.0
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Daiki Ueno
Stanislav Zidek
: Regression, Reopened
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2014-11-05 10:36 EST by Aleš Mareček
Modified: 2017-08-01 12:52 EDT (History)
7 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)


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 Aleš Mareček 2014-11-05 10:36:07 EST
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.
Comment 3 Stef Walter 2014-11-11 06:03:43 EST
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 4 RHEL Product and Program Management 2014-11-11 06:05:46 EST
Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.
Comment 14 Karel Srot 2016-08-29 06:15:06 EDT
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.
Comment 18 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.