Bug 1222595 - Suppress PIN values in 'getcert list' output
Summary: Suppress PIN values in 'getcert list' output
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: certmonger
Version: 6.6
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Jan Cholasta
QA Contact: Kaleem
URL: https://fedorahosted.org/certmonger/t...
Depends On:
TreeView+ depends on / blocked
Reported: 2015-05-18 15:10 UTC by Nalin Dahyabhai
Modified: 2015-07-22 07:17 UTC (History)
5 users (show)

Fixed In Version: certmonger-0.77.4-1.el6
Doc Type: Bug Fix
Doc Text:
Previously, after the user ran the "getcert list" command, the output included the PIN value if it was set for the certificate. Consequently, the user could unintentionally expose the PIN, for example by publicly sharing the output of the command. With this update, the "getcert list" output only contains a note that a PIN is set for the certificate. As a result, the PIN value itself is no longer displayed in the "getcert list" output.
Clone Of:
Last Closed: 2015-07-22 07:17:45 UTC

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:1379 normal SHIPPED_LIVE certmonger bug fix and enhancement update 2015-07-20 17:58:28 UTC

Description Nalin Dahyabhai 2015-05-18 15:10:58 UTC
Description of problem:
People can use plaintext PINs instead of storing them in files, and when asking for assistance, they can forget to prune a PIN value from the output.

Version-Release number of selected component (if applicable):
Everything before 0.77.4.

How reproducible:

Steps to Reproduce:
1. getcert request -P pinvalue ...
2. getcert list

Actual results:
Output includes "pin='pinvalue'".

Expected results:
Output notes only that a PIN is set.

Comment 3 Kaleem 2015-05-20 10:20:29 UTC

certmonger version:

snip from automation log:

:: [   LOG    ] :: BZ1222595: Suppress PIN values in 'getcert list' output

:: [  BEGIN   ] :: Running 'cat /tmp/tmp.n05cAsr1y8/temp_bz1222595.out'
Number of certificates and requests being tracked: 1.
Request ID '20150519174524':
	stuck: no
	key pair storage: type=NSSDB,location='/tmp/tmp.n05cAsr1y8',nickname='certtest',token='NSS Certificate DB',pin set
	certificate: type=NSSDB,location='/tmp/tmp.n05cAsr1y8',nickname='certtest',token='NSS Certificate DB'
	issuer: CN=Certificate Authority,O=TESTRELM.TEST
	subject: CN=cloud-qe-2.testrelm.test,O=TESTRELM.TEST
	expires: 2017-05-19 17:45:25 UTC
	key usage: digitalSignature,nonRepudiation,keyEncipherment,dataEncipherment
	eku: id-kp-serverAuth,id-kp-clientAuth
	pre-save command: 
	post-save command: 
	track: yes
	auto-renew: yes
:: [   PASS   ] :: Command 'cat /tmp/tmp.n05cAsr1y8/temp_bz1222595.out' (Expected 0, got 0)
:: [   PASS   ] :: File '/tmp/tmp.n05cAsr1y8/temp_bz1222595.out' should contain 'status: MONITORING' 
:: [   PASS   ] :: File '/tmp/tmp.n05cAsr1y8/temp_bz1222595.out' should contain 'pin set' 
:: [   PASS   ] :: File '/tmp/tmp.n05cAsr1y8/temp_bz1222595.out' should not contain 'xxxxxxxx'

Comment 4 errata-xmlrpc 2015-07-22 07:17:45 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.


Note You need to log in before you can comment on or make changes to this bug.