pkcsslotd(8) [debian 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)

PKCSCONF(1)							   openCryptoki 						       PKCSCONF(1)

NAME

       pkcsconf - configuration utility for the pkcsslotd daemon

SYNOPSIS

       pkcsconf [-itsmlIupPh] [-c slotnumber -U userPIN -S SOPin -n newpin]

DESCRIPTION

       The pkcsconf utility displays and configures the state of the pkcsslotd daemon and the tokens managed by the daemon.

COMMAND SUMMARY

       -i	 display PKCS11 info

       -t	 display token info

       -s	 display slot info

       -m	 display mechanism list

       -l	 display slot description

       -I	 initialize token

       -u	 initialize user PIN

       -p	 set the user PIN

       -P	 set the SO PIN

       -c SLOT	 specify the token slot for the operation

       -U USERPIN
		 the current user pin (for use when changing the user pin; -u and -p options); if not specified, user will be prompted

       -S SOPIN  the current Security Officer (SO) pin (for use when changing the SO pin; -P option); if not specified, user will be prompted

       -n NEWPIN the  new  pin	(for  use  when changing either the user pin or the SO pin; -u, -p and -P options); if not specified, user will be
		 prompted

       -h	 show usage information

SEE ALSO

       opencryptoki(7),
       pkcsslotd(8).

3.0								     May 2007							       PKCSCONF(1)