Brad Hards cf029fd41d Add certificate unit test into build.
svn path=/trunk/kdesupport/qca/; revision=503478
2006-01-29 11:49:05 +00:00
2005-04-01 22:57:48 +00:00
2006-01-16 20:10:38 +00:00
2006-01-16 20:11:45 +00:00
2005-08-01 03:15:35 +00:00
2005-06-24 23:15:26 +00:00
2003-09-17 01:31:55 +00:00
2005-08-01 06:56:44 +00:00
2005-08-02 12:22:06 +00:00
2005-08-01 03:16:36 +00:00
2006-01-16 20:12:20 +00:00

Qt Cryptographic Architecture (QCA)
-----------------------------------

Author: Justin Karneges <justin@affinix.com>


About QCA
---------
This library provides an easy API for a range of cryptographic
features, including SSL/TLS, X.509 certificates, SASL, symmetric
ciphers, public key ciphers, hashes and much more.

Functionality is supplied via plugins.  This is useful for avoiding
dependence on a particular crypto library and makes upgrading easier,
as there is no need to recompile your application when adding or
upgrading a crypto plugin.  Also, by pushing crypto functionality into
plugins, your application is free of legal issues, such as export
regulation.


Building from CVS/SVN
---------------------

First, compile and install the 'qconf' program.  You'll need the CVS
version of it, and here are the instructions:

export CVSROOT=:pserver:anonymous@cvs.anywise.org:/psi
cvs login
cvs co qconf

Then compile qconf using the usual "./configure, make, make install"
procedure.

Finally, go into the QCA source tree and type 'qconf'.  You should now
have a configure script to execute.

When you execute that script, you should see something like the following:

     Configuring Qt Cryptographic Architecture (QCA) ...
     Verifying Qt 4 build environment ... ok
     Checking for certstore ... using bundled

     Good, your configure finished.  Now run /usr/bin/gmake.

If so, you can just run (g)make to build QCA. If not, have a look at
conf.log to see what might have gone wrong.

Description
No description provided
Readme 5.8 MiB
Languages
C++ 96.8%
CMake 2.2%
C 0.7%
Perl 0.2%