* [ISSUE] Package request:
@ 2022-07-20 17:46 dirkson
2022-07-24 9:04 ` [ISSUE] [CLOSED] Package request: uacme sgn
0 siblings, 1 reply; 2+ messages in thread
From: dirkson @ 2022-07-20 17:46 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1091 bytes --]
New issue by dirkson on void-packages repository
https://github.com/void-linux/void-packages/issues/38155
Description:
### Package name
uacme
### Package homepage
https://github.com/ndilieto/uacme
### Description
An ACMEv2 client written in C. Basically a Let'sEncrypt client. I think just making the binary available is enough - The rest of the config is specific to each user.
For our distro it would depend on openssl and libcurl .
Releases are provided as git tags in the upstream/latest branch, as per the readme. Anything here ( https://github.com/ndilieto/uacme/tags ) with the tag 'upstream/x.x.x' is considered a release. This is an unusual method of packaging releases, but I don't see where it fails to meet any void requirements because of it.
I've been using this in a light production environment since 2020. I believe I started using it because it was the only Let'sEncrypt client I could find that would allow me to get an ECC cert.
### Does the requested package meet the quality requirements?
System, Compiled
### Is the requested package released?
Yes
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2022-07-24 9:04 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-07-20 17:46 [ISSUE] Package request: dirkson
2022-07-24 9:04 ` [ISSUE] [CLOSED] Package request: uacme sgn
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).