Name

Module mod Specify a PKCS#11 module (or library) to load.moz-cert path, -z path Tests a Mozilla-like keypair generation and certificate request. Specify the path to the certificate file.verbose, -v Causes pkcs11-tool to be more verbose. This does not affect OpenSC debugging level! Hello everyone, I have a built in BT4 module DW380, how can I enable continuity on this device? Using bcrmpatchram2. firmwareREpo Tried C.A.T: Boot progress went about 60-70% then Panic. PS: BT information in System Information app Hardware, Features, and Settings: Name: Trung’s MacBook. Installing the PKCS #11 Module for Mozilla Products When you obtain a KCA certificate with the Kerberized Certificate Authority Provider for Network Identity Manager, it places the certificate in the Windows 'My' Certificate Store, which is the default location for storing personal certificates. This is a java native wrapper, based on JNA of standard methods to access smart cards (pkcs11, pc/sc, openct, libusb).Goals of this projects are:. interoperability: it can work on any platform where JNA runs: Windows, Linux, Mac (and one day even Android). modularity: you don't need to include pc/sc support if you only use pkcs11. ease of integration: it depends only on few required libraries.

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, keysand certificates stored on the token. User PIN authentication is performed for those operations that require it.

Options

--login, -l

Authenticate to the token before performing other operations. This option is not needed if a PIN is provided on the command line.
--pinpin, -ppin
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 orif it is embedded in a script.

This option will also set the --login option.

--so-pinpin
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.
--init-token
Initializes a token: set the token label as well as a Security Officer PIN (the label must be specified using --label).
--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.
--change-pin, -c
Change the user PIN on the token
--test, -t
Performs some tests on the token. This option is most useful when used with either --login or --pin.
--show-info, -I
Displays general token information.
--list-slots, -L
Displays a list of available slots on the token.
--list-mechanisms, -M
Displays a list of mechanisms supported by the token.
Pkcs-11 Module For High Sierra Mac
--list-objects, -O
Displays a list of objects.
--sign, s
Sign some data.
--hash, -h
Hash some data.
--mechanismmechanism, -mmechanism
Use the specified mechanism for token operations. See -M for a list of mechanisms supported by your token.
--keypairgen, -k
Generate a new key pair (public and private pair.)
--write-objectid, -wpath
Write a key or certificate object to the token. path points to the DER-encoded certificate or key file.
--typetype, -ytype
Specify the type of object to operate on. Examples are cert, privkey and pubkey.
--idid, -did
Specify the id of the object to operate on.
--labelname, -aname
Specify the name of the object to operate on (or the token label when --init-token is used).
--slotid
Specify the id of the slot to use.
--slot-descriptiondescription
Specify the description of the slot to use.
--slot-indexindex
Specify the index of the slot to use.
--token-labellabel
Specify the label of token. Will be used the first slot, that has the inserted token with this label.
--set-idid, -eid
Set the CKA_ID of the object.
--attr-frompath
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.
--input-filepath, -ipath
Specify the path to a file for input.
Pkcs-11 module for high sierra machine learning
--output-filepath, -opath

Pkcs-11 Module For High Sierra Machine Learning

Specify the path to a file for output.
--modulemod
Specify a PKCS#11 module (or library) to load.
--moz-certpath, -zpath
Tests a Mozilla-like keypair generation and certificate request. Specify the path to the certificate file.
--verbose, -v
Causes 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-zeronumber.

Installing the PKCS #11 Module

Proxy Server supports Public Key Cryptography Standard (PKCS) #11, which defines theinterface used for communication between SSL and PKCS #11 modules. PKCS #11modules are used for standards-based connectivity to SSL hardware accelerators.Imported certificates and keys for external hardware accelerators are stored in the secmod.db file, which is generated when the PKCS #11 module is installed.The file is located in the server-root/alias directory.

Using the Tool modutil to InstallPKCS #11 Modules

You can install PKCS #11 modules in the form of .jar filesor object files using the modutil tool.

To Install PKCS #11 modules using the Tool modutil

  1. Make sure that all servers, including the Administration Server,have been stopped.

  2. Go to the server-root/alias directorycontaining the databases.

  3. Add server-root/bin/proxy/admin/bin toyour PATH.

  4. Locate modutil in server-root/bin/proxy/admin/bin.

  5. Set the environment.

    • On UNIX: setenv

      LD_LIBRARY_PATHserver-root/bin/proxy/lib:${LD_LIBRARY_PATH}

    • On Windows, add it to the PATH

      LD_LIBRARY_PATHserver-root/bin/proxy/bin

      You can find the PATH for your computer listed underserver-root/proxy-admserv/start.

  6. In a terminal window, type modutil.

    Theoptions will be listed.

  7. Perform the actions required.

    For example, to addthe PKCS #11 module in UNIX, enter:

    modutil -add (name of PKCS#11 file) -libfile (yourlibfile for PKCS #11) -nocertdb-dbdir. (your db directory)

Exporting with the tool pk12util

Using pk12util enabless you to export certificatesand keys from your internal database and import them into an internal or externalPKCS #11 module. You can always export certificates and keys to your internaldatabase, but most external tokens will not allow you to export certificatesand keys. By default, pk12util uses certificate and keydatabases named cert8.db and key3.db.

To Export a Certificate and Key From an Internal Database

  1. Go to the server-root/alias directorycontaining the databases.

  2. Add server-root/bin/proxy/admin/bin toyour PATH.

  3. Locate pk12util in server-root/bin/proxy/admin/bin.

  4. Set the environment.

    • On UNIX:

      setenvLD_LIBRARY_PATH/server-root/bin/proxy/lib:${LD_LIBRARY_PATH}

    • On Windows, add it to the PATH

      LD_LIBRARY_PATHserver-root/bin/proxy/bin

      You can find the PATH for your computer listed under: server-root/proxy-admserv/start.

  5. In a terminal window, type pk12util.

    The options will be listed.

  6. Perform the actions required.

    For example, in UNIXtype

    pk12util -o certpk12 -n Server-Cert [-d /server/alias][-P https-test-host]

  7. Type the database password.

  8. Type the pkcs12 password.

To Import a Certificate and Key Into an Internal orExternal PKCS #11 Module

  1. Go to the server-root/alias directorycontaining the databases.

  2. Add server-root/bin/proxy/admin/bin toyour PATH.

  3. Locate pk12util in server-root/bin/proxy/admin/bin.

  4. Set the environment.

    For example:

    • On UNIX:

      setenvLD_LIBRARY_PATH/server-root/bin/proxy/lib:${LD_LIBRARY_PATH}

      • On Windows, add to the PATH

        LD_LIBRARY_PATHserver-root/bin/proxy/bin

        You can find the PATH for your computer listed under server-root/proxy-admserv/start.

  5. In a terminal window, type pk12util.

    The options will be listed.

  6. Perform the actions required.

    For example, in UNIXenter:

    pk12util -i pk12_sunspot [-d certdir][-h “nCipher”][-Phttps-jones.redplanet.com-jones-]

    -P mustfollow -h and must be the last argument.

    Typethe exact token name including capital letters and spaces between quotationmarks.

  7. Type the database password.

  8. Type the pkcs12 password.

Starting the Server With an External Certificate

If you install a certificate for your server into an external PKCS #11module, for example, a hardware accelerator, the server will not be able tostart using that certificate until you edit the server.xml fileor specify the certificate name as described below.

The server always tries to start with the certificate named Server-Cert.However, certificates in external PKCS #11 modules include one of the module’stoken names in their identifier. For example, a server certificate installedon an external smartcard reader called smartcard0 wouldbe named smartcard0:Server-Cert.

To start a server with a certificate installed in an external module,you must specify the certificate name for the listen socket on which it runs.

Pkcs-11 Module For High Sierra Macos

To Select the Certificate Name for a Listen Socket

If security is not enabled on the listen socket, certificate informationwill not be listed. To select a certificate name for a listen socket, youmust first ensure that security is enabled on the listen socket. For moreinformation, see Enabling Security for Listen Sockets.

Pkcs-11 Module For High Sierra Mac Os

  1. Access either the Administration Server or the Server Managerand click the Preferences tab.

  2. Click the Edit Listen Sockets link.

  3. Click the link for the listen socket that you want to associatewith a certificate.

  4. Select a server certificate from the Server Certificate Name drop-downlist for the listen socket and click OK.

    The list contains allinternal and external certificates installed.

    You could also requirethe server to start with that server certificate instead, by manually editingthe server.xml file. Change the servercertnickname attribute in the SSLPARAMS to:

    $TOKENNAME:Server-Cert

    To find what valueto use for $TOKENNAME, go to the server’s Securitytab and select the Manage Certificates link. When you log in to the externalmodule where Server-Cert is stored, its certificates are displayed in thelist in the $TOKENNAME:$NICKNAME form.

    If youdid not create a trust database,one will be created for you when you request or install a certificate foran external PKCS #11 module. The default database created has no passwordand cannot be accessed. Your external module will work, but you will not beable to request and install server certificates. If a default database hasbeen created without a password, use the Create Database page on the Securitytab to set the password.