X Certificate and Key management
Go to file
2007-04-11 11:19:22 +02:00
doc Release 0.6.1 2007-04-05 11:55:22 +02:00
img better icons 2007-02-09 00:28:29 +01:00
lang fix dist target 2007-02-14 23:10:19 +01:00
lib replace "include <Qt/" by "include <" 2007-04-11 11:19:22 +02:00
misc W32: no need to define ETC, but need to define LINUXDOC 2007-04-10 14:04:57 +02:00
ui changes to change to qmake 2007-04-09 15:58:41 +02:00
widgets replace "include <Qt/" by "include <" 2007-04-11 11:19:22 +02:00
.gitignore remove unneeded TainyCA files, cleanup build env, 2007-02-12 21:57:48 +01:00
AUTHORS documentation and key export updates 2006-12-04 07:41:49 +01:00
changelog break endless loop in chain building Bug [ 1696878 ] 2007-04-09 21:37:27 +02:00
configure changes to change to qmake 2007-04-09 15:58:41 +02:00
COPYRIGHT Typo in copyright 2006-12-29 14:04:58 +01:00
CREDITS credits for financial support added 2004-04-15 15:32:38 +00:00
INSTALL.w32 Fix openssl-cross patch 2007-04-05 10:59:40 +02:00
Makefile Release 0.6.1 2007-04-05 11:55:22 +02:00
mkxcapro.sh Version 0.6.0-pre00 2006-11-28 09:22:18 +01:00
README documentation and key export updates 2006-12-04 07:41:49 +01:00
Rules.mak W32: no need to define ETC, but need to define LINUXDOC 2007-04-10 14:04:57 +02:00
VERSION break endless loop in chain building Bug [ 1696878 ] 2007-04-09 21:37:27 +02:00
xca.pro replace "include <Qt/" by "include <" 2007-04-11 11:19:22 +02:00

-------------------=[ XCA ]=---------------------


A graphical userinterface to OpenSSL.
handling keys, generating Certificate signing requests,
handling of client and root-certificates,
as well as handling multiple CAs with signing , CRL
and certificate templates.



Requirements:
==============

for compilation, you need the following Libraries:

QT          >=  4.2.1  from http://www.troll.no
OpenSSL     >=  0.9.7  from http://www.openssl.org

GNU C++ compiler >= 3.1.0
GNU make



Installation:
=============

Configuration:
--------------
XCA comes with its own configuration tool that has no
relationship with the GNU "autoconf" and "automake" tools.
Just the naming and invokation looks like it. Thus the
usual way to configure and build a Package is the same:
$ ./configure; make; make install

If you have a special setup, you can predefine the following
variables: CC, LD, STRIP, CFLAGS, prefix. e.g.:
$ CC="ccache gcc" STRIP=: CFLAGS="-Wall -g" prefix=/opt/xca ./configure
to have a cached build and to not strip xca when installing it.
XCA expects the translationfiles in /opt/xca/share/xca/
and installs itself to /opt/xca/bin/

The header and library files were searched in:
"$QTDIR /usr /usr/X11R6 /usr/local"
and all directorys supplied at the commandline of configure.
The QT installationdir should not be supplied at the CMDline of configure
but rather written to the $QTDIR environment variable as it is done
with the most distributions.

If for example your shiny recent QT is in /home/chris/aaa/src/qt4
and your new OpenSSL is installed in /usr/local/ssl
invoke configure like this:
----------------------------------------------
$ export QTDIR=/home/chris/aaa/src/qt4
$ ./configure /usr/local/ssl
Found: qobject.h at /home/chris/aaa/src/qt4/include
Found: libqt.so at /home/chris/aaa/src/qt4/lib
Found: openssl/opensslv.h at /usr/local/ssl/include
Found: libcrypto.so at /usr/local/ssl/lib
The Versions of the used libraries are:
.....
$
---------------------------------------------

This writes all found settings, vars and headers to
"Local.mak".

After Local.mak was created by configure it can be used
and modified for your needs.

Building:
-----------
The Makefiles do support parallel builds (-j)
targets:
all, xca :  builds the app
install  :  installs the app
headers  :  UICs the headers in ui/ needed by other files.
clean    :  deletes all builded files
distclean:  deletes also Local.mak
xca.exe  :  W32 executable
setup.exe:  W32 installer
xca.app  :  OS-X application
xca.dmg  :  OS-X installation image

Installing:
------------
make destdir=/my/virtual/root
provides /my/virtual/root/ as root-directory for installation
to be mounted by others as root or as installdir for
package builders.


Running/invoking:
=================

a detailed manual can be found in docs/


----------------------------------------------------------
if there are any questions regarding this software,
dont hesitate to contact me:

christian@hohnstaedt.de


$Id$