security/py-pem: Add py-pem 21.2.0

pem is an MIT-licensed Python module for parsing and splitting of PEM files,
i.e. Base64-encoded DER keys and certificates.

It runs on Python 3.7+, has no dependencies, and does not attempt to interpret
the certificate data in any way.

It's born from the need to load keys, certificates, trust chains, and DH
parameters from various certificate deployments: some servers (like Apache)
expect them to be a separate file, others (like nginx) expect them concatenated
to the server certificate and finally some (like HAProxy) expect key,
certificate, and chain to be in one file.

Additionally to the vanilla parsing code, pem also contains helpers for Twisted
that save a lot of boilerplate code.
This commit is contained in:
Po-Chuan Hsieh 2023-01-30 20:21:12 +08:00
parent 3de7714032
commit 0421e03a23
No known key found for this signature in database
GPG Key ID: 9A4BD10F002DD04B
4 changed files with 37 additions and 0 deletions

View File

@ -935,6 +935,7 @@
SUBDIR += py-pass-git-helper
SUBDIR += py-passlib
SUBDIR += py-pbkdf2
SUBDIR += py-pem
SUBDIR += py-pgpdump
SUBDIR += py-pgpy
SUBDIR += py-plaso

19
security/py-pem/Makefile Normal file
View File

@ -0,0 +1,19 @@
PORTNAME= pem
PORTVERSION= 21.2.0
CATEGORIES= security python
MASTER_SITES= PYPI
PKGNAMEPREFIX= ${PYTHON_PKGNAMEPREFIX}
MAINTAINER= sunpoet@FreeBSD.org
COMMENT= Easy PEM file parsing in Python
WWW= https://github.com/hynek/pem
LICENSE= MIT
LICENSE_FILE= ${WRKSRC}/LICENSE
USES= python:3.7+
USE_PYTHON= autoplist concurrent distutils
NO_ARCH= yes
.include <bsd.port.mk>

3
security/py-pem/distinfo Normal file
View File

@ -0,0 +1,3 @@
TIMESTAMP = 1674588064
SHA256 (pem-21.2.0.tar.gz) = c491833b092662626fd58a87375d450637d4ee94996ad9bbbd42593428e93e5a
SIZE (pem-21.2.0.tar.gz) = 35546

14
security/py-pem/pkg-descr Normal file
View File

@ -0,0 +1,14 @@
pem is an MIT-licensed Python module for parsing and splitting of PEM files,
i.e. Base64-encoded DER keys and certificates.
It runs on Python 3.7+, has no dependencies, and does not attempt to interpret
the certificate data in any way.
It's born from the need to load keys, certificates, trust chains, and DH
parameters from various certificate deployments: some servers (like Apache)
expect them to be a separate file, others (like nginx) expect them concatenated
to the server certificate and finally some (like HAProxy) expect key,
certificate, and chain to be in one file.
Additionally to the vanilla parsing code, pem also contains helpers for Twisted
that save a lot of boilerplate code.