This release has been yanked by its maintainers, and will be ignored by installers, except when explicitly specified.
Reason given by maintainers: Superseded by certbot-dns-glesys
GleSYS DNS Authenticator for Certbot
This allows automatic completion of Certbot’s DNS01 challange for domains managed on GleSYS DNS.
Installing
$ pip install certbot-glesys
Usage
Create an API key with the following permissions:
domain:list
domain:listrecords
domain:addrecord
domain:deleterecord
Don’t forget to give access to the appropriate IP-address range. If you want to be able to run the client from anywhere, enter 0.0.0.0/0.
To use the authenticator you need to provide some required options:
- --certbot-glesys:auth-credentials (required)
INI file with user and password for your GlesSYS API user.
The credentials file must have the following format:
certbot_glesys:auth_user = CL00000
certbot_glesys:auth_password = apikeygoeshere
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:
$ certbot certonly \
--authenticator certbot-glesys:auth \
--certbot-glesys: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.
Disclaimer
This plugin is neither affiliated with nor endorsed by GleSYS Internet Services AB.
Changelog
Version 0.2.0
Released on 23rd April 2018
This is a breaking change since it requires the domain:list permission.
Added proper support for sub domain guessing, pull request #4 (@Lillecarl)
Version 0.1.1
Released on 15th March, 2018
Bumped default propagation time to 90 seconds to improve reliability
Fixed wrong base url in GlesysDomainApiClient, pull request #2 (@montaniasystemab)
Version 0.1.0
Released on 30th September, 2017
Initial release
Metadata
Release files for certbot-glesys 0.2.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 | Actions |
|---|---|---|---|---|
| certbot-glesys-0.2.0.tar.gz | 5.4 kB | Without provenance | Details for certbot-glesys-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| certbot_glesys-0.2.0-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for certbot_glesys-0.2.0-py2.py3-none-any.whl |
Total release size: 12.2 kB
Release files / certbot-glesys-0.2.0.tar.gz
| Download URL | certbot-glesys-0.2.0.tar.gz |
|---|---|
| Size | 5.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
316c300081d5b72bc5ed33e4057930305edb01c58fb8b3408799a92f8104e16b
|
|
BLAKE2b-256 checksum How to use checksums |
d3feaa9ef02a1440d186dadadd16bfbad4952d94bb31851bccfa4875e37ac857
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / certbot_glesys-0.2.0-py2.py3-none-any.whl
| Download URL | certbot_glesys-0.2.0-py2.py3-none-any.whl |
|---|---|
| Size | 6.8 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
c4c9b047f45afb771028620d9807d22262f2dcc4366dcc167a1596751e29d33d
|
|
BLAKE2b-256 checksum How to use checksums |
4e6cafb27216a61e7452e8e639427bfd37d207f8a1a2a71e6919331e6cb3ae4a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for certbot-glesys 0.2.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.