When adding a new PIN to an axalto/schlumberger eGate device, i get
prompted about "transport key", which isn't mentioned anywherein
pkcs15-init(1) at all.  Undocumented, obscure options are bad news,
especially when dealing with devices like smart cards which are easy
to accidentally destroy.

Here's an example:

[0 dkg@squeak ~]$ pkcs15-init --store-pin --id 02 --label ugga
New User PIN.
Please enter User PIN:
Please type again to verify:
Unblock Code for New User PIN (Optional - press return for no PIN).
Please enter User unblocking PIN (PUK):
Please type again to verify:
Transport key (External authentication key #1) required.
Please enter key in hexadecimal notation (e.g. 00:11:22:aa:bb:cc),
or press return to accept default.

To use the default transport keys without being prompted,
specify the --use-default-transport-keys option on the
command line (or -T for short), or press Ctrl-C to abort.
Please enter key [2c:15:e5:26:e9:3e:8a:19]:


But neither --use-default-transport-keys nor -T show up in
pkcs15-init(1).  grepping through the documentation turns up some info
in /usr/share/doc/opensc/SecureSetup.html and
/usr/share/doc/opensc/Pkcs15Init.html, but not enough for a regular
user to figure out what's going on.  The OPTIONS section of the man
page should either have exhaustive listing, or it should refer users
to other locally-available documentation.

I'd submit a patch, but:

 * i don't really understand what transport keys are myself, and

 * the troff source claims to be generated via docbook, and i don't
   see the docbook source in the unpacked debian package.

Let me know if i can be of more help,

sorry, but everytime I bought cryptoflex cards,
the manufacturer / redistributor sendit with some
piece of paper with the transport key on it.

the docbook documentation for the tools is in
doc/tools/*.xml.

but maybe the card documentation is a better
place? see our wiki, if you change it there,
we will pull in the latest version into
the source when building tar.gz files.

Regards, Andreas