NAME
xca - A GUI for handling X509 certificates, RSA keys,
PKCS#10 Requests and CRLs.
SYNOPSIS
xca [-v] [-k] [-r]
[-c] [-p] [-7] [-l] [-t]
[-d] [-b] [-x]
DESCRIPTION
This application is intended as CA,
certificate- and Key store. It uses a Berkeley db for storage to
have everything in one file. Supported are Certificate signing
requests (PKCS#10), Certificates (X509v3), RSA keys and Certificate
revokation lists. The signing of requests, and the creation of
selfsigned certificates is supported. Both can use templates for
simplicity. The PKI structures can be imported and exported in
several formats like PKCS#12, PEM, DER, PKCS#8, PKCS#7.
OPTIONS
A summary of options are included below.
- -v
- Show version information and exit.
- -r
- expect all following non-option arguments to be Certificate
signing requests or SPKAC requests.
- -k
- expect all following non-option arguments to be RSA keys.
- -c
- expect all following non-option arguments to be Certificates.
- -p
- expect all following non-option arguments to be PKCS#12 files.
- -7
- expect all following non-option arguments to be PKCS#7 files.
- -l
- expect all following non-option arguments to be Revocation
lists.
- -t
- expect all following non-option arguments to be XCA templates.
- -d
- expect the following argument to be the database name to use.
- -b
- expect the following argument to be the basedirectory for the
database(s) OIDs and database logs.
- -x
- Exit after processing all commandline options. Usually after
importing the items in -k -r -c -p -7 -l -t the application
will startup as usual. With the -x option given it will exit
after finishing the import dialog. This is usefull if xca is used
as default application for viewing certificates, keys or
requests.
SEE ALSO
A more detailed HTML documentation can be found in
the doc directory, in the "Help" menu of the application or on
http://xca.sf.net
AUTHOR
This manual page was written by Christian Hohnstaedt
<christian@hohnstaedt.de>