[no description] https://git.osdyson.ru/mirror/pkgsrc/atom?h=pkgsrc_2008Q2 2008-04-25T22:30:47Z 2008-04-25T22:30:47Z tnn tnn 2008-04-25T22:30:47Z urn:sha1:c6e64afb294b7b10b3318c312a6b9c9c35fc98a3 2008-04-25T22:16:20Z tnn tnn 2008-04-25T22:16:20Z urn:sha1:3de0ac33f8a5b342bc9e65f5cf1d184cd87736ee 2008-04-25T20:39:06Z joerg joerg 2008-04-25T20:39:06Z urn:sha1:36c2fb54a849271ea467f4aa4c33371f1856e400 - 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-01-18T05:06:18Z tnn tnn 2008-01-18T05:06:18Z urn:sha1:1c8e24b168b5909ecc586bdbb660570b490d92ef on packages that are affected by the switch from the openssl 0.9.7 branch to the 0.9.8 branch. ok jlam@ 2007-05-05T00:03:54Z agc agc 2007-05-05T00:03:54Z urn:sha1:3eeb87bba0560f44a90649fad4085830451f1581 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.