Bug 730654 - opencryptoki: don't add root to pkcs11 group
Summary: opencryptoki: don't add root to pkcs11 group
Alias: None
Product: Fedora
Classification: Fedora
Component: openCryptoki
Version: rawhide
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Michal Schmidt
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: 732756 833818
TreeView+ depends on / blocked
Reported: 2011-08-15 09:19 UTC by Tomas Hoger
Modified: 2012-07-03 09:49 UTC (History)
3 users (show)

Fixed In Version: opencryptoki-2.4.2-1.fc18
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 732756 (view as bug list)
Last Closed: 2012-07-03 09:49:25 UTC

Attachments (Terms of Use)
Patch attempting to fix the bug (1.25 KB, patch)
2011-08-15 15:18 UTC, Steve Grubb
no flags Details | Diff

Description Tomas Hoger 2011-08-15 09:19:49 UTC
Description of problem:
Upon installation of the opencryptoki packages, pkcs11 group is created and root user is added to the group:


The purpose of this group is to restrict access to pkcsslotd's shared memory (which is root:pkcs11, 660).  root user should not need access to the group to be able to access the shared memory.  However, if root is removed from pkcs11, root can no longer use opencryptoki.

This is due to a bogus check in the attach_shared_memory(), that requires explicit group membership regardless of the current effective privileges:


Note that elsewhere in the code, similar check is only done when both uid and euid != 0:


It's unclear to me what the benefit of the check should be, as shared memory permissions are still checked.

Steps to Reproduce:
It can be demonstrated that root does not need to be in the pkcs11.  Start root shell with privileges that do not include pkcs11 group.  Ensure that root belongs to the group in the /etc/group.

// check what we do not currently have pkcs11 group
# id
uid=0(root) gid=0(root) groups=0(root),1(bin),2(daemon),3(sys),4(adm),6(disk),10(wheel) context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023

// but it is in the /etc/group
# id root
uid=0(root) gid=0(root) groups=0(root),1(bin),2(daemon),3(sys),4(adm),6(disk),10(wheel),498(pkcs11)

// root can use opencryptoki
# pkcsconf -t
Token #1 Info:
        Label: IBM OS PKCS#11                  
        Manufacturer: IBM Corp.                       
        Model: IBM SoftTok     

// remove root from the group
# vigr

# id root
uid=0(root) gid=0(root) groups=0(root),1(bin),2(daemon),3(sys),4(adm),6(disk),10(wheel)

// root can no longer use opencryptoki, even though effective permissions
// have not changed
# pkcsconf -t
Error initializing the PKCS11 library: 0x2 (CKR_HOST_MEMORY)

CCing Steve, as he's recently been after killing root supplementary groups, which can be a problem for programs what do not drop group privileges correctly.

Comment 1 Steve Grubb 2011-08-15 15:18:39 UTC
Created attachment 518278 [details]
Patch attempting to fix the bug

This probably fixes the bug.

Comment 2 Tomas Hoger 2011-08-16 07:41:24 UTC
+ relevant spec file change.

Does it make sense to leave similar code in new_host.c mentioned in comment #0?

Comment 3 Steve Grubb 2011-08-16 12:17:05 UTC
Those start off like this:
if ( userid != 0 && euserid != 0 ) { // Root or effective Root is ok

So, I think they are OK. Also note that bug 724007 is asking for supplemental groups to be dropped.

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