ACME Management Server (ACMEMS): Now "Macen"
Deprecated: The software has been rename to "Macen"! Please, update to that one to receive future updates.
LetsEncrypt supports issuing free certificates by communication via ACME - the Automatically Certificate Management Evaluation protocol.
This tools is yet another ACME client ... but as a client/server model.
Why yet another ACME client
Some aspects are special:
- ACME handling can be put into own VM / container ...: The server can be placed into an own VM, container, network segment to limit the security risk on compromised systems.
- Only the server requires all the ACME dependencies: The clients require only a SSL tool like OpenSSL and a HTTP client like wget or curl, no python, no build tools. Python with python-acme and its dependencies (PyOpenSSL, Cryptography, ...) is only needed for the server.
- Supports distributed web servers: All
.well-known/acme-challengesrequests for all domains can be served directly by the server. This makes it easy to validate domains when using multiple web server in distributed or fail-over fashion by forwarding all.well-known/acme-challengesrequests. - Only the server needs the ACME account information: It is not that security relevant, but only the ACME Management Server needs access to the account information / key for the ACME server like LetsEncrypt.
- Caching CSR signs: The returned signed certificate of a CSR is cached until the certificate is nearly expired (per default two week). If two machines have manual shared a key and CSR and they reusing both, they will both get from ACMEMS the same certificate back.
License
GPL License
Copyright (c) 2015-2025, Malte Swart
1 maintainer
Metadata
1 maintainer
Release files for acme-mgmtserver 0.5.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| acme_mgmtserver-0.5.0.tar.gz | 2.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| acme_mgmtserver-0.5.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 5.2 kB
Release files / acme_mgmtserver-0.5.0.tar.gz
| Download URL | acme_mgmtserver-0.5.0.tar.gz |
|---|---|
| Size | 2.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9ded437378be4576754ba21c617105ddc99b166dd980701771cf999ed8e1b336
|
|
BLAKE2b-256 checksum How to use checksums |
e3335e1bbc971ddbebf48736ce646eda52f29b6a350cac0c5e0e46196738f80e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.8.15
|
Release files / acme_mgmtserver-0.5.0-py3-none-any.whl
| Download URL | acme_mgmtserver-0.5.0-py3-none-any.whl |
|---|---|
| Size | 3.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dbc77067c3ca91bc373fcecd4fa26283560bbb7bce181d86a1728b504bdc55be
|
|
BLAKE2b-256 checksum How to use checksums |
65bcb9f83c6d9aac130274601e4ea04609bf93ce2c1f01707b8352af49f46812
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.8.15
|
Security for acme-mgmtserver 0.5.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
