letsencrypt/acme client implemented as a shell-script
https://github.com/lukas2511/dehydrated
A client for signing certificates with an ACME-server (currently only provided by letsencrypt) implemented as a relatively simple bash-script.
It uses the openssl utility for everything related to actually handling keys and certificates, so you need to have that installed.
Other dependencies are: curl, sed, grep, mktemp (all found on almost any system, curl being the only exception)
Current features:
* Signing of a list of domains
* Signing of a CSR
* Renewal if a certificate is about to expire or SAN (subdomains) changed
* Certificate revocation
- Developed at security:dehydrated
- Sources inherited from project openSUSE:Factory
-
4
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout openSUSE:Backports:SLE-15-SP4:FactoryCandidates/dehydrated && cd $_ - Create Badge
Refresh
Refresh
Source Files
| Filename | Size | Changed |
|---|---|---|
| README.Fedora | 0000000163 163 Bytes | |
| README.hooks | 0000000223 223 Bytes | |
| README.maintainer | 0000006272 6.13 KB | |
| acme-challenge.conf.apache.in | 0000000176 176 Bytes | |
| acme-challenge.conf.nginx.in | 0000000528 528 Bytes | |
| dehydrated-0.6.5.tar.gz | 0000082274 80.3 KB | |
| dehydrated-0.6.5.tar.gz.asc | 0000000488 488 Bytes | |
| dehydrated-rpmlintrc | 0000000048 48 Bytes | |
| dehydrated.changes | 0000015818 15.4 KB | |
| dehydrated.cron.in | 0000000249 249 Bytes | |
| dehydrated.keyring | 0000002353 2.3 KB | |
| dehydrated.service.in | 0000000420 420 Bytes | |
| dehydrated.spec | 0000009381 9.16 KB | |
| dehydrated.timer | 0000000168 168 Bytes | |
| dehydrated.tmpfiles.d | 0000000135 135 Bytes |
Revision 17 (latest revision is 27)
Dominique Leuenberger (dimstar_suse)
accepted
request 817721
from
Daniel Molkentin (dmolkentin)
(revision 17)
- Update maintainer file and package description, remove features that are better described in the (upstream maintained) man page. - Remove potentially harmful scriptlet (bsc#1154167). Documented transition case in the maintainer README. Unlikely enough. The versions that have not transitioned yet would be broken for more than two years now.
Comments 0