Bug 119363

Summary: LTC7125-Start of openCryptoki slot daemon - pkcsslotd - for the 1st time give message chgrp: invalid group name `g+rw'
Product: Red Hat Enterprise Linux 3 Reporter: IBM Bug Proxy <bugproxy>
Component: crypto-utilsAssignee: Phil Knirsch <pknirsch>
Status: CLOSED ERRATA QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: high    
Version: 3.0CC: rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: s390   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-05-12 01:24:58 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:
Bug Depends On:    
Bug Blocks: 119235    

Description IBM Bug Proxy 2004-03-29 21:29:28 UTC
The following has be reported by IBM LTC:  
Start of openCryptoki slot daemon - pkcsslotd - for the 1st time give
message chgrp: invalid group name `g+rw'
Hardware Environment: z990

Software Environment: RHEL3 U2 beta1

Steps to Reproduce:
1. load the z90crypt crypto device driver
2. Start the pkcsslotd daemon provided by openCryptoki - 

root@rhel3u21 init.d]# ./pkcsslotd start 
                                         
Starting pkcsslotd:                      
chgrp: invalid group name `g+rw'


Additional Information:

It looks like the 1st time the pkcsslotd daemon is started,
the pkcs_slot script provided by openCryptoki in 
/usr/lib/pkcs11/methods
creates the /etc/pkcs11 directory and sets owner & permissions,
using these commands - 

# Check for the existance of the directories
if [ ! -d /etc/pkcs11 ]                     
then                                        
        mkdir -p /etc/pkcs11                
        chgrp pkcs11 /etc/pkcs11            
        chgrp -R g+rw /etc/pkcs11           
fi 

It looks like that chgrp -R g+rw should be changed to a chmod.
When pkcsslotd runs for the 1st time, it puts out the message - 

Starting pkcsslotd:                      
chgrp: invalid group name `g+rw'

The slot deamon does start successfully, and, the /etc/pkcs11
directory is created successfully.
And once it's created, the message does not re-occur.

Comment 1 IBM Bug Proxy 2004-04-01 15:45:33 UTC
----- Additional Comments From yoder1.com  2004-04-01 10:46 -------
This bug is fixed in openCryptoki CVS Head. Grab that by doing: 
 
cvs -d :pserver:anoncvs.com:/usr/cvs/opencryptoki 
 
l/p: anoncvs/anoncvs 
 
CVS is the best way to get openCryptoki right now, there have been problems 
uploading the latest tarballs to the developerWorks site.   
 
Other bugs since 2.1.3 have been fixed in CVS as well, the version you grab 
from CVS should be 2.1.5. (Use CVS tag openCryptoki-2-1-5 if you like, but it 
should match the code in CVS Head.) 

Comment 4 Florian La Roche 2004-04-09 15:38:08 UTC
openCryptoki 2.1.5-1 is available in the beta channel, setting this to
modified.

greetings,

Florian La Roche


Comment 5 IBM Bug Proxy 2004-04-25 03:56:01 UTC
----- Additional Comments From khoa.com  2004-04-24 23:58 -------
Please verify this on Update2 when it comes out and close the bug report
if everything is ok.  Thanks. 

Comment 6 IBM Bug Proxy 2004-04-26 12:22:59 UTC
----- Additional Comments From miket.com  2004-04-26 08:09 -------
Installed RHEL3 Update2 Beta 2, and installed the openCryptoki rpms from 
the RedHat Channel - 
openCryptoki-2.1.5-1.s390.rpm
(and on 64-bit) - 
openCryptoki-2.1.5-1.s390x.rpm

pkcsslotd then started successfully with no error message - 
[root@rhel3u22 init.d]# ./pkcsslotd start
                                         
Starting pkcsslotd: 

Closing the bug. 

Comment 7 John Flanagan 2004-05-12 01:24:58 UTC
An errata has been issued which should help the problem described in this bug report. 
This report is therefore being closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, please follow the link below. You may reopen 
this bug report if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2004-216.html