Commit graph

5 commits

Author SHA1 Message Date
Max Brazhnikov
5f3906c936 Use correct path for strip.
Reported by:	Marco Broder (marco.broeder at gmx.eu) via e-mail
2009-07-08 20:43:02 +00:00
Max Brazhnikov
6458100fba Clean up, remove stale dependencies 2009-03-19 12:03:34 +00:00
Martin Wilke
921d171a35 - Remove a typo 2009-03-02 20:00:17 +00:00
Martin Wilke
45ba55420e - Fix build with OpenSSL from ports
PR:		132097
Submitted by:	Matt Dawson <matt@chronos.org.uk>
Thanks to:	dinoex@
2009-03-02 18:55:39 +00:00
Martin Wilke
7e45300e38 Taking a hint from the similarly-named Java Cryptography Architecture,
QCA aims to provide a straightforward and cross-platform crypto
API, using Qt datatypes and conventions. QCA separates the API from
the implementation, using plugins known as Providers. The advantage
of this model is to allow applications to avoid linking to or
explicitly depending on any particular cryptographic library. This
allows one to easily change or upgrade crypto implementations
without even needing to recompile the application. QCA should work
everywhere Qt does, including Windows/Unix/MacOSX.

Capabilities:
TLS, CMS, X.509, RSA, DSA, Diffie-Hellman, PKCS#7, PKCS#12, SHA0,
SHA1, SHA224, SHA256, SHA384, SHA512, MD2, MD4, MD5, RIPEMD160,
Blowfish, DES, 3DES, AES128, AES192, AES256, CAST5, HMAC(SHA1, MD5,
RIPEMD160), PBKDF1(MD2, SHA1), PBKDF2(SHA1)

WWW: http://delta.affinix.com/qca/
2008-08-05 00:12:57 +00:00