Bug 730903

Summary: opencryptoki: document implications of the pkcs11 group membership
Product: Red Hat Enterprise Linux 6 Reporter: Tomas Hoger <thoger>
Component: opencryptokiAssignee: Dan Horák <dhorak>
Status: CLOSED ERRATA QA Contact: BaseOS QE Security Team <qe-baseos-security>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.1CC: mvadkert, ovasik
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: opencryptoki-2.4-2.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-06 11:48:48 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Possible man page change none

Description Tomas Hoger 2011-08-16 07:49:17 UTC 
Description of problem:
The documentation we (and also upstream) provide with opencryptoki packages mentions, that users using opencryptoki need to be members of the pkcs11 group.  It does not currently mention the real privileges granted by adding a user to the group (ability to block other applications using opencryptoki from using opencryptoki/devices, ability to execute arbitrary code as other users using opencryptoki, see bug #730635).

Upstream assumes that all pkcs11 members are fully trusted.  Such assumption should be documented.
Comment 3 Tomas Hoger 2011-09-05 11:40:28 UTC 
Created attachment 521484 [details]
Possible man page change

Possible fix.  opencryptoki.7 sounds to me as a better place to have the warning, with pkcsslotd.8 referring to it.  Some further wording-polish is welcome.
Comment 6 Tomas Hoger 2011-09-20 06:25:40 UTC 
(In reply to comment #3)
> Created attachment 521484 [details]
> Possible man page change

Merged upstream:
http://opencryptoki.git.sourceforge.net/git/gitweb.cgi?p=opencryptoki/opencryptoki;a=commitdiff;h=7744b6224e80848596ac80a07745c7a588eef2a0
Comment 7 errata-xmlrpc 2011-12-06 11:48:48 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.

http://rhn.redhat.com/errata/RHBA-2011-1572.html