certbot-onion
onion-csr-01 Authenticator plugin for Certbot
This plugin allows certbot to request certificates for .onion domains using the onion-csr-01 challenge type,
signing the request with the key of the hidden service.
Installation
pip install certbot-onion
Usage
certbot --server https://acme.api.acmeforonions.org/directory certonly -d 5anebu2glyc235wbbop3m2ukzlaptpkq333vdtdvcjpigyb7x2i2m2qd.onion --authenticator onion-csr
The important arguments here is: --authenticator onion-csr
Configuration arguments
--onion-csr-torrc-file /etc/tor/torrc- Provides the path to thetorrcfile, hidden service directories are discovered from this file.--onion-csr-hs-dir /var/lib/tor/example_hs/- Provides the path to the hidden service directory, this can be specified multiple times for multiple domains.
If your torrc is in the standard location of /etc/tor/torrc then you do not need to specify any configuration arguments.
Metadata
Release files for certbot-onion 0.4.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_onion-0.4.0.tar.gz | 9.8 kB | Without provenance | Details for certbot_onion-0.4.0.tar.gz |
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| certbot_onion-0.4.0-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.whl | CPython 3.8 | CPython 3.8 | Linux glibc 2.17+ x86-64 | Details for certbot_onion-0.4.0-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
| certbot_onion-0.4.0-cp38-cp38-manylinux_2_17_i686.manylinux2014_i686.whl | CPython 3.8 | CPython 3.8 | Linux glibc 2.17+ x86-32 | Details for certbot_onion-0.4.0-cp38-cp38-manylinux_2_17_i686.manylinux2014_i686.whl |
Total release size: 4.0 MB
Release files / certbot_onion-0.4.0.tar.gz
| Download URL | certbot_onion-0.4.0.tar.gz |
|---|---|
| Size | 9.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4dc9f93175114b53f264ce89a86eab44ccfc9a29d8d23716f3745b38427508b9
|
|
BLAKE2b-256 checksum How to use checksums |
d2f56ce254bbcdff2f1630a0e382fcab5df570ed7a447119fd7ffddd92c23870
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.9.22
|
Release files / certbot_onion-0.4.0-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | certbot_onion-0.4.0-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 2.0 MB |
| Tags | CPython 3.8 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
081e2d0e6f3da2aa0d7d16b669821e489ce434e92c8849c8bc4bf78bd84a9b60
|
|
BLAKE2b-256 checksum How to use checksums |
5ae4a50c945019b73250404cf200480e2aa03841518fca94d86ff13be9b52658
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.9.22
|
Release files / certbot_onion-0.4.0-cp38-cp38-manylinux_2_17_i686.manylinux2014_i686.whl
| Download URL | certbot_onion-0.4.0-cp38-cp38-manylinux_2_17_i686.manylinux2014_i686.whl |
|---|---|
| Size | 2.0 MB |
| Tags | CPython 3.8 Linux glibc 2.17+ x86-32 |
|
SHA-256 checksum How to use checksums |
448e51dba07aeff849fd3b3fd753ff8be36789a0bc15bee3981f4584343e3d7a
|
|
BLAKE2b-256 checksum How to use checksums |
1bc1453c93bb516d318fdef66556d212d31a13d4f68f4073fd2242edee1d678d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.9.22
|
Security for certbot-onion 0.4.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.