opensc/doc/tools/westcos-tool.1.xml

<?xml version="1.0" encoding="UTF-8"?>
<refentry id="westcos-tool">
	<refmeta>
		<refentrytitle>westcos-tool</refentrytitle>
		<manvolnum>1</manvolnum>
		<refmiscinfo class="productname">OpenSC</refmiscinfo>
		<refmiscinfo class="manual">OpenSC Tools</refmiscinfo>
		<refmiscinfo class="source">opensc</refmiscinfo>
	</refmeta>

	<refnamediv>
		<refname>westcos-tool</refname>
		<refpurpose>utility for manipulating data structures
			on westcos smart cards</refpurpose>
	</refnamediv>

	<refsynopsisdiv>
		<cmdsynopsis>
			<command>westcos-tool</command>
			<arg choice="opt"><replaceable class="option">OPTIONS</replaceable></arg>
		</cmdsynopsis>
	</refsynopsisdiv>

	<refsect1>
		<title>Description</title>
		<para>
			The <command>westcos-tool</command> utility is used to manipulate
			the westcos data structures on 2 Ko smart cards. Users can create PINs,
			keys and certificates stored on the token. User PIN authentication is
			performed for those operations that require it.
		</para>
	</refsect1>

	<refsect1>
		<title>Options</title>
		<para>
			<variablelist>
				<varlistentry>
					<term><option>--reader, r</option> num</term>
					<listitem><para>
					Use the given reader. The default is the first reader with a card.
					</para></listitem>
				</varlistentry>

				<varlistentry>
					<term><option>--wait, -w</option></term>
					<listitem><para>Wait for a card to be inserted</para></listitem>
				</varlistentry>

				<varlistentry>
					<term><option>--generate-key, -g</option></term>
					<listitem><para>Generate a private key on smart card. The smart card must be
					not finalized and a PIN must be installed (ie. file for PIN must be created, see option
					-i). By default key length is 1536 bits. User authentication is required for
					this operation. </para></listitem>
				</varlistentry>

				<varlistentry>
					<term><option>--overwrite-key, -o</option></term>
					<listitem><para>Overwrite the key if there is already a key on card.</para></listitem>
				</varlistentry>

				<varlistentry>
					<term>
						<option>--key-length</option> length,
						<option>-l</option> length
					</term>
					<listitem><para>Change the length of private key, use with <option>-g</option>.
						</para></listitem>
				</varlistentry>

				<varlistentry>
					<term><option>--install-pin, -i</option></term>
					<listitem><para>Install PIN file in token, you must provide PIN value
					with <option>-x</option>.</para></listitem>
				</varlistentry>

				<varlistentry>
					<term>
						<option>--pin-value</option> value,
						<option>-x</option> value
					</term>
					<listitem><para>set value of PIN.</para></listitem>
				</varlistentry>

				<varlistentry>
					<term>
						<option>--puk-value</option> value,
						<option>-y</option> value
					</term>
					<listitem><para>set value of PUK (or value of new PIN for change PIN
					command see <option>-n</option>).</para></listitem>
				</varlistentry>

				<varlistentry>
					<term><option>--change-pin, -n</option></term>
					<listitem><para>Changes a PIN stored on the token. User authentication
					is required for this operation.</para></listitem>
				</varlistentry>

				<varlistentry>
					<term><option>--unblock-pin, -u</option></term>
					<listitem><para>Unblocks a PIN stored on the token. Knowledge of the
					PIN Unblock Key (PUK) is required for this operation.</para></listitem>
				</varlistentry>

				<varlistentry>
					<term>
						<option>--certificate</option> file,
						<option>-t</option> file
					</term>
					<listitem><para>Write certificate file in PEM format to the
					card. User authentication is required for this operation.</para></listitem>
				</varlistentry>

				<varlistentry>
					<term><option>--finalize, -f</option></term>
					<listitem><para>Finalize the card. Once finalized the default key is invalidated so PIN and PUK
					can't be changed anymore without user authentication. Warning,
					un-finalized are insecure because PIN can be changed without user authentication (knowledge of default key
					is enough).</para></listitem>
				</varlistentry>

				<varlistentry>
					<term>
						<option>--read-file</option> path,
						<option>-j</option> path
					</term>
					<listitem><para>Get the file path the file is written
					on disk with path name. User authentication
					is required for this operation.</para></listitem>
				</varlistentry>

				<varlistentry>
					<term>
						<option>--write-file</option> path,
						<option>-k</option> path
					</term>
					<listitem><para>Put the file with name path from disk
					to card the file is written in path. User authentication
					is required for this operation.</para></listitem>
				</varlistentry>

				<varlistentry>
					<term><option>--help, -h</option></term>
					<listitem><para>Print help message on screen.</para></listitem>
				</varlistentry>

				<varlistentry>
					<term><option>-v</option></term>
					<listitem><para>Causes <command>westcos-tool</command> to be more
					verbose. Specify this flag several times to enable debug output
					in the OpenSC library.</para></listitem>
				</varlistentry>

			</variablelist>
		</para>
	</refsect1>

	<refsect1>
		<title>Authors</title>
		<para><command>westcos-tool</command> was written by
		Francois Leblanc <email>francois.leblanc@cev-sa.com</email>.</para>
	</refsect1>

</refentry>