aboutsummaryrefslogtreecommitdiff
path: root/security/qca-ossl/Makefile
Commit message (Collapse)AuthorAgeFilesLines
* Fix build with OpenSSL 1.0Max Brazhnikov2010-05-211-1/+1
| | | | | | | | PR: ports/146615 Reported by: Gerard Seibert <gerard at seibercom.net> Notes: svn path=/head/; revision=254754
* Use correct path for strip.Max Brazhnikov2009-07-081-2/+2
| | | | | | | Reported by: Marco Broder (marco.broeder at gmx.eu) via e-mail Notes: svn path=/head/; revision=237444
* Clean up, remove stale dependenciesMax Brazhnikov2009-03-191-11/+13
| | | | Notes: svn path=/head/; revision=230395
* - Remove a typoMartin Wilke2009-03-021-1/+1
| | | | Notes: svn path=/head/; revision=229366
* - Fix build with OpenSSL from portsMartin Wilke2009-03-021-2/+5
| | | | | | | | | PR: 132097 Submitted by: Matt Dawson <matt@chronos.org.uk> Thanks to: dinoex@ Notes: svn path=/head/; revision=229349
* Taking a hint from the similarly-named Java Cryptography Architecture,Martin Wilke2008-08-051-0/+35
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/ Notes: svn path=/head/; revision=218046