Bug 1871137 - Review Request: acme-sh - An lightweight ACME client written purely in SH
Summary: Review Request: acme-sh - An lightweight ACME client written purely in SH
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Fedora
Classification: Fedora
Component: Package Review
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Nobody's working on this, feel free to take it
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-08-21 12:05 UTC by Christopher Engelhard
Modified: 2020-08-26 10:35 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-08-26 10:35:16 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Christopher Engelhard 2020-08-21 12:05:10 UTC
Spec URL: https://pagure.io/fedora-rpm-addons/raw/master/f/acme-sh/acme-sh.spec
SRPM URL: https://download.copr.fedorainfracloud.org/results/lcts/fedora-rpm-addons/fedora-rawhide-x86_64/01620104-acme-sh/acme-sh-2.8.6-4.1.fc34.src.rpm

Description: Acme.sh is an ACME client written purely in POSIX Shell language. It implements the full ACME protocol and supports both ACMEv1 and ACMEv2 as well as ACMEv2 wildcard certificates. It can automatically issue, renew and install certificates and supports a wide variety of DNS provider APIs for DNS-01 challenges.
Homepage: https://github.com/acmesh-official/acme.sh

Fedora Account System Username: lcts

Notes:
 - The software is actually called acme.sh, but that is not an allowed package name, correct?
 - This program offers options to (automatically) install and update itself from the commandline. Doing so will effectively "hide" the rpm-installed version from the user. Should I patch the script to disable these options (fairly easy to do) or stay close to upstream & trust the user not to use them?

Comment 1 Christopher Engelhard 2020-08-26 10:35:16 UTC
Withdrawing this for now, as there are some security issues with acme.sh that I need to patch first.


Note You need to log in before you can comment on or make changes to this bug.