Search Criteria
Package Details: acmetool 0.0.67-5
Package Actions
Git Clone URL: | https://aur.archlinux.org/acmetool.git (read-only, click to copy) |
---|---|
Package Base: | acmetool |
Description: | An easy-to-use command line tool for automatically acquiring certificates from ACME servers (such as Let's Encrypt) |
Upstream URL: | https://github.com/hlandau/acme |
Licenses: | MIT |
Submitter: | Thermi |
Maintainer: | None |
Last Packager: | Thermi |
Votes: | 4 |
Popularity: | 0.000000 |
First Submitted: | 2016-08-26 09:00 (UTC) |
Last Updated: | 2019-10-25 00:20 (UTC) |
Dependencies (3)
- bash (bash-devel-static-gitAUR, bash-devel-gitAUR, busybox-coreutilsAUR, bash-gitAUR)
- libcap
- go (go-gitAUR, gcc-go-gitAUR, gcc-go-snapshotAUR, gcc-go) (make)
Latest Comments
1 2 Next › Last »
cyqsimon commented on 2022-04-04 08:04 (UTC) (edited on 2022-04-04 08:10 (UTC) by cyqsimon)
I think it's fair to consider
acmetool
as abandonware for now.If you (like me) have previously used its redirect feature (handles ACME over HTTP and redirects everything else to HTTPS), you may wish to check out acme-redirect. It's simple, intuitive, configurable, written in Rust, and just overall very comfortable to use. I built it from source and deployed it on my RHEL8 server without trouble within half an hour.
For the moment the only problem I've found is that it doesn't generate a file that contains both the full chain and key (which
haproxy
prefers), but I have already put in a PR for that.emmieaur commented on 2022-03-29 00:56 (UTC) (edited on 2022-03-29 00:56 (UTC) by emmieaur)
Build fails, I don't use go so I'm not sure what the fix is, but this looks like a build tool change:
bsdice commented on 2021-05-18 09:42 (UTC)
I also switched, to acme.sh which I can recommend. A bit quirky with all those options but works for me. Let's Encrypt needs occasional updates for its API but Hugo seems busy otherwise to implement all the changes. +1 abandonware for me as well.
Thermi commented on 2021-05-18 09:16 (UTC)
FredBezies just orphaned the package via an AUR request. I don't use it anymore and the dev, hlandau, is not declaring any stable version, so I won't try to maintain it anymore. From my side, it's basically abandonware now.
Thermi commented on 2020-07-23 23:32 (UTC)
I'll bump the PKG version once the new version is stable.
bsdice commented on 2019-10-25 00:13 (UTC)
Is 0.0.67-4 for anyone else broken? In prepare() I need this now:
... mv "${srcdir}/acmetool-${pkgver}" "${GOPATH}/src/github.com/hlandau/acme" ...
Sloonz commented on 2019-10-21 12:56 (UTC)
0.2.1 is beta : https://github.com/hlandau/acmetool/issues/322
grawity commented on 2019-10-21 12:24 (UTC) (edited on 2019-10-21 12:26 (UTC) by grawity)
In that case, it might be better to verify using the SHA1 hash of Git commit (which hopefully isn't going to change no matter what GitHub decides to screw up):
Speaking of which, v0.2.1 appears to have been tagged last week:
(Yes I know the
< >
are not supposed to be there. I'm not in control of what AUR's markdownifier decides to do.)Sloonz commented on 2019-10-18 20:10 (UTC)
Checksum for acmetool-0.0.67.tar.gz doesn’t checks. Just downloaded the tarball on https://github.com/hlandau/acmetool/releases, checksum is 45e458f385515b669ade4a8de6dd6800da2b61f4846bd6f573e28c51ca6805ea ; 01f78340006539c62bb86250433d2f819ab529ccd9a0aa74e140ff0fee839073 in the PKGBUILD
1 2 Next › Last »