The smartcard utility is used for all configurations related to a smartcard. It comprises the following subcommands:

1. Administration of OCF properties. (-c admin)

   This subcommand is used to list and modify any of the OCF properties. With no arguments it will list all the current properties. It can only be executed by root. Some OCF properies are:

   defaultcard

   # default card for an application

   defaultreader

   # default reader for an application

   authmechanism

   # authentication mechanism to

   validcards

   # list of cards valid for an application

   A complete listing can be obtained by using the smartcard command as described in the EXAMPLES section.

2. Loading and Unloading of applets from the smartcard (-c load) and performing initial configuration of a non-Java card.

   This subcommand administers the applets or properties on a smartcard. It can be used to load or unload applets and/or properites to and from a smartcard. The applet is a Java class file that has been run through a convertor to make the byte code JavaCard-compliant. This command can be used to load both an applet file in the standard format or a file converted to the capx format. If no -r option is specified, the loader tries to load to any connected reader, provided it has already been inserted using the smartcard -c admin command.

3. Converting card applets or properties to the capx format (-c bin2capx)

   This subcommand is used to convert a Java card applet or properties into a new format called capx before downloading it onto the smartcard. Converting to this format enables the applet developer to add applet-specific information that is useful during the downloading process and identifies the applet.

   In the following example,

   smartcard -c bin2capx -i cyberflex.bin \ -T CyberFlex aidto-000102030405060708090A0B0C0D0E0F fileID=2222 \ instanceID=2223 and more.

   if no output file is specified, a default file with the name input_filename.capx is created in the current directory. The mandatory -T option requires the user to specify the card name for which the capx file is being generated.

   The following example

   smartcard -c bin2capx -T IButton

   tells the loader eventually that the capx file contains the binary for IButton. A single capx file can hold binaries for multiple cards (1 per card.) Users can, for example, hold binary files for both CyberFlex and IButton in the same capx file as follows:

   smartcard -c bin2capx -T IButton -i IButton.jib -o file.capx

   In the following example,

   smartcard -c bin2capx -T CyberFlex -i cyberflex.bin \ -l file.capx -o file.capx

   the -l option is used to provide an already-generated capx file. The output is directed to the same capx file, resulting in capx file holding binaries for both cards.

4. Personalizing the smartcard (-c init)

   This subcommand is used to set user-specific information required by an applet on a smartcard. For example, the Sun applet requires a user name to be set on the card. This subcommand is also used to personalize information for non-Java cars.

5. Enabling and disabling the smartcard desktop login (-c {enable | disable)

The following options are supported:

-a application

Specify application name for the configuration parameter. Parameters may differ depending on the application. If no application name is specified, then ocf is the default application.

-A aid

Specify a unique alphanumeric string that identifies the applet. The aid argument must be a minimum of 5 characters and can be a maximum of 16 characters in length. If an applet with an identical aid already exists on the card, a load will result in an error.

-c

Specify subcommand name. Valid options are: admin, load, bin2capx, init, enable and disable.

-d device

Specify device on which the reader is connected (for example, /dev/cua/a).

-D

Disable a system from using smartcards.

-E

Export the keys to a file.

-i filename

Specify input file name.

-I

Import from a file.

-j classname

Specify fully-qualified class name.

-k keytype

Specify type of key (for example, challenge_response, pki.)

-l

Specify debug level (0-9), signifying level of debug information displayed.

-L

List all properties configurable in an applet.

-n readername

Specify reader name as required by the driver.

-o filename

Specify output file name.

-p propfile

Specify properties file name. This file could contain a list of property names and value pairs, in the format propertyname=value.

-P pin

Specify pin used to validate to the card.

-r userfriendlyreadername

Specify user-defined reader name where the card to be initialized is inserted.

-R

Restart the ocf server.

-s slot

Specify slot number. If a reader has multiple slots, this option specifies which slot to use for initialization. If a reader has only one slot, this option is not required. If no slot number is specified, by default the fist slot of the reader is used.

-t

Specify type of property being updated. The valid values are:

service

Updating a card service provider details.

terminal

Updating a card reader provider details.

debug

OCF trace level.

override

Override a system property of the same name.

-T cardname

Specify card name.

-u

Unload the applet specified by the application ID from the card. If no application ID is specified, all applets are unloaded from the card.

-v

Verbose mode ( displays helpful messages).

-x

Specify action to be taken. Valid values are: add, delete, or modify.

The following exit values are returned:

0

Successful completion.

1

An error occurred.

See attributes(5) for descriptions of the following attributes:

ocfserv(1M), attributes(5), smartcard(5)

The command line options contain only alphanumeric input.