diff options
| author | jdolecek <jdolecek@pkgsrc.org> | 2007-12-20 20:37:21 +0000 |
|---|---|---|
| committer | jdolecek <jdolecek@pkgsrc.org> | 2007-12-20 20:37:21 +0000 |
| commit | e210ff0a0a19edc3adff9641e82d8722cb0a5ab3 (patch) | |
| tree | a53621c82b502c0e629a13c6362395c01cf7ca38 /security/qca-tls/DESCR | |
| parent | fdcf68587f496f2f05d8c2da19e3de30a7477ee5 (diff) | |
| download | pkgsrc-e210ff0a0a19edc3adff9641e82d8722cb0a5ab3.tar.gz | |
move back to version 1.0 for security/qca and re-add security/qca-tls
(for qca 1.x), so that kdenetwork3 works again
XXX these should be renamed to qca1* after current freeze
Diffstat (limited to 'security/qca-tls/DESCR')
| -rw-r--r-- | security/qca-tls/DESCR | 16 |
1 files changed, 16 insertions, 0 deletions
diff --git a/security/qca-tls/DESCR b/security/qca-tls/DESCR new file mode 100644 index 00000000000..7389c8bcb16 --- /dev/null +++ b/security/qca-tls/DESCR @@ -0,0 +1,16 @@ +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. + +Features: +* SSL/TLS +* X509 +* RSA +* Hashing (SHA1, MD5) +* Ciphers (Blowfish, 3DES, AES) |