From 49aa01eecb4573aea1eb59f88b2c75f0d03da8fa Mon Sep 17 00:00:00 2001 From: Christian Hohnstaedt Date: Fri, 9 Apr 2010 07:16:14 +0200 Subject: [PATCH] update docs --- doc/xca.sgml | 42 ++++++++++++++++++++++++++++++------------ 1 file changed, 30 insertions(+), 12 deletions(-) diff --git a/doc/xca.sgml b/doc/xca.sgml index 3231f3e6..568056c5 100644 --- a/doc/xca.sgml +++ b/doc/xca.sgml @@ -7,7 +7,7 @@ (c) by Christian Hohnstädt, christian@hohnstaedt.de -March 2010 - Version 0.9.0 +April 2010 - Version 0.9.0 @@ -533,7 +533,7 @@ The following actions with smart cards are supported: Import keys and certificates from the token. - (Import->Manage Security token) + (Token->Manage Security token) Everything you can do with other keys can be done with tokens, too. On export, only the Public key is exported. @@ -559,6 +559,15 @@ A new menu item: Token is accessible if a PKCS#11 library was loaded an Security token specific operations are collected below the menu-item Token +Manage Security token + +

+ +This is the Multi import dialog, which allows to view and select the items to be imported. +When started it reads the content of the selected token. +Additionally, it shows token information in the bottom-right corner and allows to delete and rename +items directly on the token. + Initializing tokens

@@ -580,8 +589,8 @@ The keys and certificates can be imported via the Multi-import dialog.

-To delete certificates or keys from the token they must be first imported into the XCA databse and deleted afterwards. -XCA will then ask whether the item shall also be removed from the token. +Just delete the item as usual. XCA will then ask whether the item shall also be removed from the token. +Items on the token that were not yet imported can be deleted via the "Manage security token" menu. Changing PINs @@ -593,21 +602,30 @@ The User PIN and SO PIN can be changed via the Token menu and also via

-I used the following providers for testing: +The following providers were used for testing: OpenSC: default provider for a lot of different cards and readers. - The support of Netkey 4E cards is currently weak. - Only import and using the keys is possible. For other cards - the support is probably better. - Feitian PKI cards work like a charm. + The support of Netkey 4E cards is currently restricted. + Only import and using the keys and certificates + is possible. + Feitian PKI cards work with the following restrictions: + + The cards must be initialized outside XCA with + pkcs15-init + Storing keys onto the card crashes because of + assert(0) in card-entersafe.c in + opensc-0.11.13 + Deleting items does not work, because it is not + implemented in opensc-0.11.13/card-entersafe.c. + Aladdin eToken PKIclient-5.1: Works perfectly. Read public keys from the token, write private keys to the token, generate keys on the token, write certificates to the - token and delete them from the token. + token and delete them from the token or delete them. Linux only: OpenCryptoki (IBM): may be used as a pure software token, but also supports TPMs and other IBM crypto processors @@ -616,8 +634,8 @@ I used the following providers for testing:

-For interoperabilitytests I used the Aladdin eToken together with the -Aladdin PKIclient 5.1 software and OpenSC with the feitian PKI-card. +For interoperability tests I used the Aladdin eToken together with the +Aladdin PKIclient 5.1 software and OpenSC with the Feitian PKI-card. Aladdin: /usr/lib/libeTPkcs11.so Feitian: /usr/lib/opensc-pkcs11.so (default)