le_client
This is yet another ACME/Let’s Encrypt client. It’s inspired by acme-tiny, but does things differently.
Requirements
The client is written in Python 3. It’s incompatible with Python 2.x at the moment.
There are no dependencies on any third-party Python modules. The code should run fine on a bare Python setup, without anything from PyPI.
You need openssl command-line executable available for use in PATH. It’s used for keys and certificate request parsing.
Features and limitations
Does not know anything about servers or software. Its only purpose is to obtain a signed certificate.
Currently, the only supported challenge type is http-01 (webroot).
Does not require any fancy privileges.
It needs to access the certificate request, have write access to /.well-known/acme-challenge/ and can output the obtained certificate to a file or on stdout.
It works with either local account key file, or can use a special remote service that can sign requests.
That was the primary reason why I wrote my own client: I didn’t want to keep an account’s private key on the untrusted machine.
Currently, it only supports EC-256 account keys. It’s easy to add other curve sizes and RSA support, but I’m lazy.
It’s meant to be either usable as a standalone command-line utility, or as a simple Python library.
Remote account key protocol
This client supports a special mode of operation where it doesn’t have a local account private key, but asks a remote service to sign whatever payload it needs.
A remote service is located at a single URL, served over HTTPS. To authenticate the client, CLI currently supports only HTTP Basic Authentication.
To sign, we send POST request to a given URL, appending nonce query parameter, and sending the payload as the POST body. We expect the server to answer with 200 OK an return a JWS as a response.
That’s the whole protocol description.
License
Copyright (c) 2016, Aleksey Zhukov
This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
See LICENSE file for more information.
Metadata
Release files for le-client 0.2
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 |
|---|---|---|---|---|
| le-client-0.2.tar.gz | 9.9 kB | Without provenance | Details for le-client-0.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| le_client-0.2-py3.4.egg | Legacy Egg format | - | - | Details for le_client-0.2-py3.4.egg |
Total release size: 36.4 kB
Release files / le-client-0.2.tar.gz
| Download URL | le-client-0.2.tar.gz |
|---|---|
| Size | 9.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8f47a9c16fc9ce1908a9bc7bec00b227061a7f54c21d016e1cabac1d5ec6c207
|
|
BLAKE2b-256 checksum How to use checksums |
287f9b313945434bfc4d8117c31174a0b9228912080cada68c9ceb181707f19f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / le_client-0.2-py3.4.egg
| Download URL | le_client-0.2-py3.4.egg |
|---|---|
| Size | 26.4 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
1f5ae405a74df44bb3165b713c0798a52321204b4494984fcbb1017dc8c30d92
|
|
BLAKE2b-256 checksum How to use checksums |
40bc6fbc4111a6470aaae3e3018ab38f30260d39a7d421cc469583f2f357f641
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for le-client 0.2
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.