kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/security/py-SSLCrypto/Makefile

30 lines
718 B
Makefile
Raw Normal View History

Update PYTHON_VERSIONS_COMPATIBLE - assume that Python 2.4 and 2.5 are compatible and allow checking for fallout. - remove PYTHON_VERSIONS_COMPATIBLE that are obsoleted by the 2.3+ default. Modify the others to deal with the removals.
2008-04-25 22:39:06 +02:00
# $NetBSD: Makefile,v 1.3 2008/04/25 20:39:11 joerg Exp $
Initial import of py-SSLCrypto-0.1.1 into the Packages Collection. SSLCrypto is a package for Python that dramatically eases the task of adding encryption to Python programs. It provides a unified API that is almost totally compatible with that of ezPyCrypto, except that it takes advantage of the OpenSSL Crypto Library to deliver massive improvements in speed and security. After using ezPyCrypto myself, I found that while it performed ok with smaller public key sizes, it proved impossibly slow with larger keys. This slowness, resulting from non-optimal code in its backend (the Python Cryptography Toolkit) meant that on a 1.5 GHz Athlon XP, it was taking several minutes to generate 4096-bit keys. Completely unacceptable if you need real security. Performance is absolutely critical for an encryption API. If slowness deters people from using adequate-sized keys, security will be severely compromised, almost to the extent that there's little point in using encryption in the first place.
2007-05-05 02:03:54 +02:00
#
DISTNAME= SSLCrypto-0.1.1
PKGNAME= ${PYPKGPREFIX}-${DISTNAME}
Per the process outlined in revbump(1), perform a recursive revbump on packages that are affected by the switch from the openssl 0.9.7 branch to the 0.9.8 branch. ok jlam@
2008-01-18 06:06:18 +01:00
PKGREVISION= 1
Initial import of py-SSLCrypto-0.1.1 into the Packages Collection. SSLCrypto is a package for Python that dramatically eases the task of adding encryption to Python programs. It provides a unified API that is almost totally compatible with that of ezPyCrypto, except that it takes advantage of the OpenSSL Crypto Library to deliver massive improvements in speed and security. After using ezPyCrypto myself, I found that while it performed ok with smaller public key sizes, it proved impossibly slow with larger keys. This slowness, resulting from non-optimal code in its backend (the Python Cryptography Toolkit) meant that on a 1.5 GHz Athlon XP, it was taking several minutes to generate 4096-bit keys. Completely unacceptable if you need real security. Performance is absolutely critical for an encryption API. If slowness deters people from using adequate-sized keys, security will be severely compromised, almost to the extent that there's little point in using encryption in the first place.
2007-05-05 02:03:54 +02:00
CATEGORIES= security python
MASTER_SITES= http://www.freenet.org.nz/python/SSLCrypto/
MAINTAINER= pkgsrc-users@NetBSD.org
HOMEPAGE= http://www.freenet.org.nz/python/SSLCrypto/
COMMENT= Python bindings for openssl
DEPENDS+= py24-pyrex>=0.9.4.1:../../lang/py-pyrex
Update PYTHON_VERSIONS_COMPATIBLE - assume that Python 2.4 and 2.5 are compatible and allow checking for fallout. - remove PYTHON_VERSIONS_COMPATIBLE that are obsoleted by the 2.3+ default. Modify the others to deal with the removals.
2008-04-25 22:39:06 +02:00
PYTHON_VERSIONS_ACCEPTED= 25 24
Initial import of py-SSLCrypto-0.1.1 into the Packages Collection. SSLCrypto is a package for Python that dramatically eases the task of adding encryption to Python programs. It provides a unified API that is almost totally compatible with that of ezPyCrypto, except that it takes advantage of the OpenSSL Crypto Library to deliver massive improvements in speed and security. After using ezPyCrypto myself, I found that while it performed ok with smaller public key sizes, it proved impossibly slow with larger keys. This slowness, resulting from non-optimal code in its backend (the Python Cryptography Toolkit) meant that on a 1.5 GHz Athlon XP, it was taking several minutes to generate 4096-bit keys. Completely unacceptable if you need real security. Performance is absolutely critical for an encryption API. If slowness deters people from using adequate-sized keys, security will be severely compromised, almost to the extent that there's little point in using encryption in the first place.
2007-05-05 02:03:54 +02:00
PLIST_SUBST+= PYSITELIB=${PYSITELIB:Q}
do-build:
cd ${WRKSRC} && ${PYTHONBIN} setup.py build
do-install:
cd ${WRKSRC} && ${PYTHONBIN} setup.py install
.include "../../lang/python/application.mk"
.include "../../security/openssl/buildlink3.mk"
.include "../../mk/bsd.pkg.mk"
Reference in a new issue Copy permalink