summaryrefslogtreecommitdiff
path: root/devel/qt4-designer/files/patch-tools__designer__src__designer__assistantclient.cpp
diff options
context:
space:
mode:
authorMartin Wilke <miwi@FreeBSD.org>2008-08-05 00:12:57 +0000
committerMartin Wilke <miwi@FreeBSD.org>2008-08-05 00:12:57 +0000
commit7e45300e38fd5feba84c6d4da0c94b81fe10df9a (patch)
treee7d2edf5d8cdca64b9e42d6137b56f8a52b6cf64 /devel/qt4-designer/files/patch-tools__designer__src__designer__assistantclient.cpp
parent- Fix Build after qt4 update (diff)
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/
Diffstat (limited to 'devel/qt4-designer/files/patch-tools__designer__src__designer__assistantclient.cpp')
0 files changed, 0 insertions, 0 deletions