packages/net/acme-common/files, branch master

acme-common: move nftables rule to hook

2026-07-04T15:27:50Z

The nftables rule in acme-common partially works, but it races against the acme.sh and uacme client. While the client is performing the renew the rule is being deleted because the client is run in the background. This change moves the rule management to the hook instead. While duplicate rules could be created, the benefits outway the potential costs. It is unknown how many installations issue/renew multiple certificates. Signed-off-by: Michael A Cassaniti

acme-common: migrate uacme config paramaters

2026-04-14T07:38:06Z

migrate old uacme specific config parameters into acme-common format. Signed-off-by: Seo Suchan

acme-acme.sh: support --cert-profile option

2026-01-03T14:19:18Z

acme 3.1.2 added a new --cert-profile option to request specific certificates. This makes it possible to request shortlived six day certificates from Letsencrypt. Signed-off-by: Norman Gehrsitz

acme.sh: add `abort` service command and improve interactive messages

2025-10-08T18:27:32Z

For runs started interactively, improve messaging and allow a run to be aborted with `service acme abort`. Signed-off-by: Aditya Bhargava

acme.sh: move to procd to ensure logging gets to syslog

2025-10-08T18:27:32Z

acme.sh error output never made it to the syslog, so: * Add procd setup to catch stderr * Make sure a message goes to syslog if acme.sh dies due to SIGINT Signed-off-by: Aditya Bhargava

acme-common: support listen_port option

2025-10-02T11:14:11Z

listen_port option allows to redefine the default 80/443 port used in standalone/alpn challenges. It's also useful for other types of challenges which require accepting a connection on some TCP port so we need to expose it via nft as well. Signed-off-by: Vladimir Kochnev

acme-common: cleanup acme start crontab migration

2025-09-03T21:25:08Z

The '/etc/init.d/acme start' crontab migration should also delete the existing '/etc/init.d/acme start' line. Otherwise, on every sysupgrade that carries forward existing configurations, a new '0 0 * * * /etc/init.d/acme renew' line is added to the crontab. Furthermore, do not add an 'acme renew' crontab line if it already exists. Signed-off-by: Satadru Pramanik, DO, MPH, MEng

acme: remove crontab entry if service is stopped

2025-04-01T20:53:08Z

Until now it was not possible to stop the acme service, because the handling was done via cron. With this change, the acme handler can now be stopped by calling '/etc/init.d/acme' stop. This call removes the entry from the crontab. Signed-off-by: Florian Eckert

acme: remove lock handling

2025-04-01T20:53:08Z

Since procd is now used, the call of '/etc/init.d/acme' does not have to be locked separately. This code block can therefore be removed. Signed-off-by: Florian Eckert

acme: fix service_triggers on config change

2025-04-01T20:53:08Z

In the current implementation, the config change trigger is no longer set at boot time. This is because during boot, only the '$CHALLENGE_DIR' is created with the boot function. The 'start_service' is first called by first cron call at midnight. This call is installing the service_triggers reload handling. To fix this, add a new extra_command 'renew' that is responsible to renew the acme. This function is called from cron and the start_service function does the rest. * Create directories * Install service reload trigger form acme config change Fixes: 76f17ab15b (acme-common: Create challenge directory on boot) Signed-off-by: Florian Eckert