Page MenuHomeFreeBSD

New port, security/acme.sh: ACME protocol client written in shell
ClosedPublic

Authored by jrm on Apr 7 2017, 5:22 PM.
Tags
None
Referenced Files
F81649203: D10308.diff
Fri, Apr 19, 11:12 AM
Unknown Object (File)
Thu, Apr 11, 7:57 AM
Unknown Object (File)
Fri, Mar 22, 10:58 PM
Unknown Object (File)
Fri, Mar 22, 10:58 PM
Unknown Object (File)
Fri, Mar 22, 10:58 PM
Unknown Object (File)
Fri, Mar 22, 10:58 PM
Unknown Object (File)
Mar 9 2024, 1:51 PM
Unknown Object (File)
Jan 7 2024, 6:38 AM

Details

Summary
Test Plan

portlint -C: OK
testport: OK (poudriere: 11.0-RELEASE-p1, amd64)

Questions:

  • Should the shebang be replaced with #/bin/sh ?
  • Which of the following do you prefer?

    a) Create an acme user/group and do acme.sh --install. With this option, we will have to use sensible defaults for --home, --certhome, and --config-home.

    b) Use pkg-message to tell users the basics for getting started (e.g. acme.sh --install... etc.)

    c) Let users read the documentation.

I am leaning towards b) or c). a) might be easier in some cases, but it removes
control from the user.

Diff Detail

Repository
rP FreeBSD ports repository
Lint
No Lint Coverage
Unit
No Test Coverage
Build Status
Buildable 8586
Build 8900: arc lint + arc unit

Event Timeline

Remove files/. It was unintentionally added.

Creating a user for a shell script seems silly. Create a pkg-message to tell users the basics and have it also point at the docs. (So, B and C)

This revision is now accepted and ready to land.Apr 8 2017, 2:41 PM

Creating a user for a shell script seems silly. Create a pkg-message to tell users the basics and have it also point at the docs. (So, B and C)

The idea is that all operations should be done as a non privileged user. So, adding one with the port is a good idea.

I am going to play with this, and see if I can create the non-priv user. I'm keen to use this ASAP.

We use this and would be really happy to have a port of it

Trying to contact jrm over IRC, but bad time of day I think. I'm happy to do the work and commit it with him as maintainer, or if he prefers, I would take over. Either way is OK by me.

dvl, rehashing our IRC conversation, I'm OK if you take over. Feel free to make changes and do as you wish wrt to maintaiership.

This revision was automatically updated to reflect the committed changes.