ANX DNS Authenticator for Certbot
This allows automatic completion of Certbot's DNS01 challange for domains managed on ANX DNS
Important information
PLEASE NOTE THAT ONE OF THE DEPENDENCIES TO THE LIBRARY INCLUDED A BAD INSTALL_REQUIRES. THIS WAS FIXED IN 0.1.6.
Installing
$ pip install certbot-anx
Usage
The plugin requires a API key that is created here: http://dyn.anx.se/users/users.jsf?i=2
To use the authenticator you need to provide some required options:
--certbot-anx:credentials (required)
ANX API credentials INI file. (default: None)
The credentials file must have the folling format:
certbot_anx:api_key = codegoeshere
For safety reasons the file must not be world readable. You can solve this by running:
$ chmod 600 credentials.ini
Then you can run certbot using:
$ sudo certbot certonly \
--authenticator certbot-anx:auth \
--certbot-anx:auth-credentials credentials.ini \
-d domain.com
If you want to obtain a wildcard certificate you can use the
--server https://acme-v02.api.letsencrypt.org/directory flag and the domain
-d *.domain.com
1 maintainer
Metadata
1 maintainer
Release files for certbot-anx 0.1.6
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 | Actions |
|---|---|---|---|---|
| certbot_anx-0.1.6.tar.gz | 4.0 kB | Without provenance | Details for certbot_anx-0.1.6.tar.gz |
Release files / certbot_anx-0.1.6.tar.gz
| Download URL | certbot_anx-0.1.6.tar.gz |
|---|---|
| Size | 4.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d89f6881ca57507294a7996aab475231c1ffd95caf75826aeb0b3430519fddf6
|
|
BLAKE2b-256 checksum How to use checksums |
1bccd2524de8c32e88d266159fce185717aec2beb6ff2e42e0d31e097e7e08c1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.0
|
Security for certbot-anx 0.1.6
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.
