| Port details |
- qca-ossl QCA OpenSLL plugin
- 2.0.0.b3_4 security
 =7      2.0.0.b3_4Version of this port present on the latest quarterly branch. - Maintainer: kde@FreeBSD.org
- Port Added: 2008-08-05 00:13:32
- Last Update: 2015-01-12 16:33:17
- SVN Revision: 376838
- People watching this port, also watch:: libao, desktop-file-utils, font-misc-meltho, font-bh-lucidatypewriter-100dpi
- License: not specified in port
- WWW:
- http://delta.affinix.com/qca/
- Description:
- 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/
 cgit ¦ GitHub ¦ GitHub ¦ GitLab ¦ 
- Manual pages:
- FreshPorts has no man page information for this port.
- pkg-plist: as obtained via:
make generate-plist - There is no configure plist information for this port.
- Dependency lines:
-
- qca-ossl>0:security/qca-ossl
- No installation instructions:
- This port has been deleted.
- PKGNAME: qca-ossl
- Flavors: there is no flavor information for this port.
- distinfo:
- There is no distinfo for this port.
No package information for this port in our database- Sometimes this happens. Not all ports have packages. Perhaps there is a build error. Check the fallout link:
- Dependencies
- NOTE: FreshPorts displays only information on required and default dependencies. Optional dependencies are not covered.
- Build dependencies:
-
- libcrypto.so.8 : security/openssl
- libQtCore.so : devel/qt4-corelib
- moc-qt4 : devel/qt4-moc
- qmake-qt4 : devel/qmake4
- Runtime dependencies:
-
- libcrypto.so.8 : security/openssl
- libQtCore.so : devel/qt4-corelib
- Library dependencies:
-
- libqca.so : devel/qca
- There are no ports dependent upon this port
Configuration Options:- ===> The following configuration options are available for qca-ossl-2.0.0.b3_4:
DEBUG=off: Build with debugging support
===> Use 'make config' to modify these settings
- Options name:
- N/A
- USES:
- tar:bzip2 qmake:_env
- FreshPorts was unable to extract/find any pkg message
- Master Sites:
|
Number of commits found: 13
| Commit History - (may be incomplete: for full details, see links to repositories near top of page) |
| Commit | Credits | Log message |
|---|
2.0.0.b3_4
12 Jan 2015 16:33:17
  |
tijl |
- Update devel/qca to version 2.1.0
- Plugins are no longer available separately so remove security/qca-* and
replace them with options in devel/qca
- Adjust all ports that depended on security/qca-*
- This also fixes the build of the OpenSSL plugin when OpenSSL doesn't
support SSLv2
Approved by: kde (rakuco) |
2.0.0.b3_4
29 Jul 2014 21:43:18
|
adamw |
Convert some more USE_BZIP2 to USES=tar:bzip2
Approved by: portmgr (not really, but touches unstaged ports) |
2.0.0.b3_4
20 Feb 2014 13:23:50
|
makc |
devel/qca:
- Add stage support
- Convert WITH_DEBUG to option
- Remove MAINTAINER_MODE
- Remove now needless stripping in post-install
security/qca-*:
- Convert LIB_DEPENDS to new style
- Add stage support
- Convert WITH_DEBUG to option
- Remove now needless stripping in post-install |
2.0.0.b3_4
17 Nov 2013 02:12:25
|
avilla |
- Replace QT_.*_REL with QT_.* in PLIST_SUB.
- Adapt plists.
With hat on: kde |
2.0.0.b3_4
20 Sep 2013 22:55:26
|
bapt |
Add NO_STAGE all over the place in preparation for the staging support (cat:
security) |
2.0.0.b3_4
06 Jun 2012 06:44:38
|
miwi |
- Convert USE_QT_VER=4 and QT_COMPONETS to USE_QT4
Review by: bapt, David Naylor (kde team) |
2.0.0.b3_4
03 Jul 2011 14:03:52
|
ohauer |
-remove MD5 |
2.0.0.b3_4
21 May 2010 21:42:01
|
makc |
Fix build with OpenSSL 1.0
PR: ports/146615
Reported by: Gerard Seibert <gerard at seibercom.net> |
2.0.0.b3_3
08 Jul 2009 20:43:02
|
makc |
Use correct path for strip.
Reported by: Marco Broder (marco.broeder at gmx.eu) via e-mail |
2.0.0.b3_2
19 Mar 2009 12:03:35
|
makc |
Clean up, remove stale dependencies |
2.0.0.b3_1
02 Mar 2009 20:00:17
|
miwi |
- Remove a typo |
2.0.0.b3_1
02 Mar 2009 18:55:40
|
miwi |
- Fix build with OpenSSL from ports
PR: 132097
Submitted by: Matt Dawson <matt@chronos.org.uk>
Thanks to: dinoex@ |
2.0.0.b3
05 Aug 2008 00:12:57
|
miwi |
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/ |
Number of commits found: 13
|
As an Amazon Associate I earn from qualifying purchases.