Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

pkcs11-tool(1) [centos man page]

PKCS11-TOOL(1)							   OpenSC Tools 						    PKCS11-TOOL(1)

NAME
pkcs11-tool - utility for managing and using PKCS #11 security tokens SYNOPSIS
pkcs11-tool [OPTIONS] DESCRIPTION
The pkcs11-tool utility is used to manage the data objects on smart cards and similar PKCS #11 security tokens. Users can list and read PINs, keys and certificates stored on the token. User PIN authentication is performed for those operations that require it. OPTIONS
--attr-from path Extract information from path (DER-encoded certificate file) and create the corresponding attributes when writing an object to the token. Example: the certificate subject name is used to create the CKA_SUBJECT attribute. --change-pin, -c Change the user PIN on the token --hash, -h Hash some data. --id id, -d id Specify the id of the object to operate on. --init-pin Initializes the user PIN. This option differs from --change-pin in that it sets the user PIN for the first time. Once set, the user PIN can be changed using --change-pin. --init-token Initialize a token: set the token label as well as a Security Officer PIN (the label must be specified using --label). --input-file path, -i path Specify the path to a file for input. --keypairgen, -k Generate a new key pair (public and private pair.) --label name, -a name Specify the name of the object to operate on (or the token label when --init-token is used). --list-mechanisms, -M Display a list of mechanisms supported by the token. --list-objects, -O Display a list of objects. --list-slots, -L Display a list of available slots on the token. --login, -l Authenticate to the token before performing other operations. This option is not needed if a PIN is provided on the command line. --mechanism mechanism, -m mechanism Use the specified mechanism for token operations. See -M for a list of mechanisms supported by your token. --module mod Specify a PKCS#11 module (or library) to load. --moz-cert path, -z path Test a Mozilla-like keypair generation and certificate request. Specify the path to the certificate file. --output-file path, -o path Specify the path to a file for output. --pin pin, -p pin Use the given pin for token operations. WARNING: Be careful using this option as other users may be able to read the command line from the system or if it is embedded in a script. This option will also set the --login option. --set-id id, -e id Set the CKA_ID of the object. --show-info, -I Display general token information. --sign, -s Sign some data. --slot id Specify the id of the slot to use. --slot-description description Specify the description of the slot to use. --slot-index index Specify the index of the slot to use. --token-label label Specify the label of token. Will be used the first slot, that has the inserted token with this label. --so-pin pin Use the given pin as the Security Officer PIN for some token operations (token initialization, user PIN initialization, etc). The same warning as --pin also applies here. --test, -t Perform some tests on the token. This option is most useful when used with either --login or --pin. --type type, -y type Specify the type of object to operate on. Examples are cert, privkey and pubkey. --verbose, -v Cause pkcs11-tool to be more verbose. NB! This does not affect OpenSC debugging level! To set OpenSC PKCS#11 module into debug mode, set the OPENSC_DEBUG environment variable to a non-zero number. --write-object id, -w path Write a key or certificate object to the token. path points to the DER-encoded certificate or key file. opensc 06/17/2014 PKCS11-TOOL(1)

Check Out this Related Man Page

PKCS15-TOOL(1)							   OpenSC Tools 						    PKCS15-TOOL(1)

NAME
pkcs15-tool - utility for manipulating PKCS #15 data structures on smart cards and similar security tokens SYNOPSIS
pkcs15-tool [OPTIONS] DESCRIPTION
The pkcs15-tool utility is used to manipulate the PKCS #15 data structures on smart cards and similar security tokens. Users can list and read PINs, keys and certificates stored on the token. User PIN authentication is performed for those operations that require it. OPTIONS
--aid aid Specify in a hexadecimal form the AID of the on-card PKCS#15 application to bind to. --auth-id pin, -a pin Specifies the auth id of the PIN to use for the operation. This is useful with the --change-pin operation. --change-pin Changes a PIN or PUK stored on the token. User authentication is required for this operation. --dump, -D Dump card objects. --learn-card, -L Cache PKCS #15 token data to the local filesystem. Subsequent operations are performed on the cached data where possible. If the cache becomes out-of-sync with the token state (eg. new key is generated and stored on the token), the cache should be updated or operations may show stale results. --list-applications List the on-card PKCS#15 applications --list-certificates, -c Lists all certificates stored on the token. --list-data-objects, -C Lists all data objects stored on the token. For some cards the PKCS#15 attributes of the private data objects are protected for reading and need the authentication with the User PIN. In such a case the --verify-pin option has to be used. --list-keys, -k Lists all private keys stored on the token. General information about each private key is listed (eg. key name, id and algorithm). Actual private key values are not displayed. For some cards the PKCS#15 attributes of the private keys are protected for reading and need the authentication with the User PIN. In such a case the --verify-pin option has to be used. --list-pins Lists all PINs stored on the token. General information about each PIN is listed (eg. PIN name). Actual PIN values are not shown. --list-public-keys Lists all public keys stored on the token, including key name, id, algorithm and length information. --no-cache Disables token data caching. --output filename, -o filename Specifies where key output should be written. If filename already exists, it will be overwritten. If this option is not given, keys will be printed to standard output. --read-certificate cert, -r cert Reads the certificate with the given id. --read-data-object cert, -R data Reads data object with OID, applicationName or label. --read-public-key id Reads the public key with id id, allowing the user to extract and store or use the public key. --read-ssh-key id Reads the public key with id id, writing the output in format suitable for $HOME/.ssh/authorized_keys. --reader num Forces pkcs15-tool to use reader number num for operations. The default is to use reader number 0, the first reader in the system. --unblock-pin, -u Unblocks a PIN stored on the token. Knowledge of the Pin Unblock Key (PUK) is required for this operation. --verbose, -v Causes pkcs15-tool to be more verbose. Specify this flag several times to enable debug output in the OpenSC library. --verify-pin Verify PIN after card binding and before issuing any command (without 'auth-id' the first non-SO, non-Unblock PIN will be verified) SEE ALSO
pkcs15-init(1), pkcs15-crypt(1) opensc 06/17/2014 PKCS15-TOOL(1)
Man Page

Featured Tech Videos