[Bug 225217] [NEW PORT] security/py-pycryptodomex: Cryptographic library for Python

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225217

            Bug ID: 225217
           Summary: [NEW PORT] security/py-pycryptodomex: Cryptographic
                    library for Python
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Keywords: easy, patch, patch-ready
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: freebsd-ports-bugs at FreeBSD.org
          Reporter: john at saltant.com
 Attachment #189798 maintainer-approval+
             Flags:

Created attachment 189798
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=189798&action=edit
security/py-pycryptodomex: New port

This port will be a slave to security/py-pycryptodome. It installs the same
package but in a different name space, Cryptodome instead of Crypto, and
therefore can be installed together with security/py-pycrypto if desired.

Description
===========

PyCryptodome is a fork of PyCrypto. It brings the following
enhancements with respect to the last official version of
PyCrypto (2.6.1):

* Authenticated encryption modes (GCM, CCM, EAX, SIV, OCB)
* Accelerated AES on Intel platforms via AES-NI
* First class support for PyPy
* SHA-3 (including SHAKE XOFs) and BLAKE2 hash algorithms
* Salsa20 and ChaCha20 stream ciphers
* scrypt and HKDF
* Deterministic DSA
* Password-protected PKCS#8 key containers
* Shamir's Secret Sharing scheme
* Random numbers get sourced directly from the OS (and not from
  a CSPRNG in userspace)
* Simplified install process, including better support for Windows
* Cleaner RSA and DSA key generation (largely based on FIPS 186-4)
* Major clean ups and simplification of the code base

WWW: https://pypi.python.org/pypi/pycryptodome


QA
==

portlint: OK
poudriere: OK -- testport w/py27 (default), py34, py35, py36


Notes
=====

* Set LICENSE to make portlint happy.
* Set empty CONFLICTS_INSTALL. This is the point of this port: it doesn't
conflict with security/py-pycrypto.
* Keep DISTINFO because upstream publishes a separate tarball. Alternatively,
it would be necessary to set one or more variables to reuse the distfile from
security/py-pycryptodome and also define a new pre-build target to touch
${WRKSRC}/.separate-namespace to activate a bunch of work in setup.py that
moves things from Crypto to Cryptodome.
* Define a PLIST for the slave. This is necessary because setup.py breaks
autoplist [0].


[0] https://github.com/Legrandin/pycryptodome/issues/119

-- 
You are receiving this mail because:
You are the assignee for the bug.