mirror of
https://github.com/QuasarApp/qca.git
synced 2025-05-11 10:19:33 +00:00
492ec1c0a8
discussed with Justin. It was only really supported by the Botan provider, and Botan dropped the idea in 1.6.0. Also, it never ensured that the random number was actually secure. svn path=/trunk/kdesupport/qca/; revision=620048
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 a Source package ------------------------------ See the 'INSTALL' file. Building from CVS/SVN --------------------- First, install the 'qconf' program, at least version 1.3. You can download the source here: http://delta.affinix.com/qconf/ Then, 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. You will also need to build appropriate plugins to get support for many of the QCA features.
Description
Languages
C++
96.8%
CMake
2.2%
C
0.7%
Perl
0.2%