Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

pkcsslotd(8) [centos man page]

PKCSSLOTD(8)							   openCryptoki 						      PKCSSLOTD(8)

NAME
pkcsslotd - shared memory manager for opencryptoki DESCRIPTION
The pkcsslotd daemon manages PKCS#11 objects between PKCS#11-enabled applications. When 2 or more processes are accessing the same crypto- graphic token, the daemon is notified and updates each application when the token's objects change. NOTES
Only one instance of the pkcsslotd daemon should be running on any given host. If a prior instance of pkcsslotd did not shut down cleanly, then it may leave an allocated shared memory segment on the system. The allocated memory segment can be identified by its key and can be safely removed once the daemon is stopped with the ipcrm command, such as: ipcrm -M 0x6202AB38 The daemon creates the shared memory segment with group ownership by the pkcs11 group. All non-root users that should be able to use open- Cryptoki need to be members of the group. Only trusted users should be assigned to the group, see the "SECURITY NOTE" in the opencryp- toki(7) manual page for details. SEE ALSO
opencryptoki(7), pkcsconf(1), pk_config_data(5), pkcs11_startup(1). 3.0 May 2007 PKCSSLOTD(8)

Check Out this Related Man Page

PKCSSLOTD(8)							   openCryptoki 						      PKCSSLOTD(8)

NAME
pkcsslotd - shared memory manager for opencryptoki DESCRIPTION
The pkcsslotd daemon manages PKCS#11 objects between PKCS#11-enabled applications. When 2 or more processes are accessing the same crypto- graphic token, the daemon is notified and updates each application when the token's objects change. NOTES
Only one instance of the pkcsslotd daemon should be running on any given host. If a prior instance of pkcsslotd did not shut down cleanly, then it may leave an allocated shared memory segment on the system. The allocated memory segment can be identified by its key and can be safely removed once the daemon is stopped with the ipcrm command, such as: ipcrm -M 0x6202AB38 In order to prevent a denial of service against the daemon, the shared memory segment is created with group ownership by the "pkcs11" group. Any application that requires access to a pkcs11 token must be run by a user who's a member of the "pkcs11" group. SEE ALSO
opencryptoki(7), pkcsconf(1), pk_config_data(5), pkcs11_startup(1). 2.3.1 May 2007 PKCSSLOTD(8)
Man Page

4 More Discussions You Might Find Interesting

1. HP-UX

shmat() permission denied, what's this?

I have installed an application that runs correctly for root but not other users. The application generates an error that indicates users don't have permission to attach to shared memory. A daemon process creates the shared memory segment. I've checked every permission I can think of but nothing... (2 Replies)
Discussion started by: km4hr
2 Replies

2. AIX

San:

hi We have 2 AIX nodes running with HACMP and all of them connected to SAN, Our shared storage is shark; I need to create shared volume group and I need the HACMP take a ware of it. Regards (1 Reply)
Discussion started by: h2aix
1 Replies

3. Programming

Dereferencing pointer to a shared memory struct

I have what should be a relatively simple program (fadec.c) that maps a struct from an included header file (fadec.h) to a shared memory region, but I’m struggling accessing members in the struct from the pointer returned by shmat. Ultimately, I want to access members in the shared memory structure... (2 Replies)
Discussion started by: arette
2 Replies

4. UNIX for Advanced & Expert Users

Permissions on a directory in /home for all users

Hi, I have created a shared directory on /home, where all users on a certain group have read, write and execute permissions. I did this using chmod -R g+rwx /home/shared/ The problem is, when a particular user creates a directory within /home/shared, other users are not able to write to... (8 Replies)
Discussion started by: lost.identity
8 Replies