<feed xmlns='http://www.w3.org/2005/Atom'>
<title>packages/net/acme-acmesh/files, branch master</title>
<subtitle>Mirror of packages feed</subtitle>
<id>https://git.openwrt.org/feed/packages/atom?h=master</id>
<link rel='self' href='https://git.openwrt.org/feed/packages/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/feed/packages/'/>
<updated>2026-07-04T15:27:50Z</updated>
<entry>
<title>acme-common: move nftables rule to hook</title>
<updated>2026-07-04T15:27:50Z</updated>
<author>
<name>Michael A Cassaniti</name>
</author>
<published>2026-06-22T03:17:52Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/feed/packages/commit/?id=ba08c8cb51102dc5575575fb72073170b6ef1a4b'/>
<id>urn:sha1:ba08c8cb51102dc5575575fb72073170b6ef1a4b</id>
<content type='text'>
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 &lt;michael@cassaniti.id.au&gt;
</content>
</entry>
<entry>
<title>acme-acmesh: remove duplicated notification on certificate renewal</title>
<updated>2026-07-01T12:50:15Z</updated>
<author>
<name>Juanyong Dong</name>
</author>
<published>2026-06-10T13:49:46Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/feed/packages/commit/?id=6334216e040de2470eb54685e4bb209613514a81'/>
<id>urn:sha1:6334216e040de2470eb54685e4bb209613514a81</id>
<content type='text'>
fix #29703

Signed-off-by: Juanyong Dong &lt;dongjuanyong@gmail.com&gt;
</content>
</entry>
<entry>
<title>acme-acme.sh: support --cert-profile option</title>
<updated>2026-01-03T14:19:18Z</updated>
<author>
<name>Norman Gehrsitz</name>
</author>
<published>2025-12-31T02:02:10Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/feed/packages/commit/?id=c410b896322248340c79abd783fff66c6d43881b'/>
<id>urn:sha1:c410b896322248340c79abd783fff66c6d43881b</id>
<content type='text'>
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 &lt;openwrt@gehrsitz.eu&gt;
</content>
</entry>
<entry>
<title>acme.sh: add `abort` service command and improve interactive messages</title>
<updated>2025-10-08T18:27:32Z</updated>
<author>
<name>Aditya Bhargava</name>
</author>
<published>2025-09-29T22:05:19Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/feed/packages/commit/?id=fbf38647fda3e1577257297d5815714814813abf'/>
<id>urn:sha1:fbf38647fda3e1577257297d5815714814813abf</id>
<content type='text'>
For runs started interactively, improve messaging and allow a run to be
aborted with `service acme abort`.

Signed-off-by: Aditya Bhargava &lt;rightaditya@gmail.com&gt;
</content>
</entry>
<entry>
<title>acme.sh: move to procd to ensure logging gets to syslog</title>
<updated>2025-10-08T18:27:32Z</updated>
<author>
<name>Aditya Bhargava</name>
</author>
<published>2025-09-22T07:56:17Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/feed/packages/commit/?id=76b676e4ebbb4b13dd476c626c56f72b44564e7e'/>
<id>urn:sha1:76b676e4ebbb4b13dd476c626c56f72b44564e7e</id>
<content type='text'>
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 &lt;rightaditya@gmail.com&gt;
</content>
</entry>
<entry>
<title>acme-acme.sh: support listen_port option</title>
<updated>2025-10-02T11:14:11Z</updated>
<author>
<name>Vladimir Kochnev</name>
</author>
<published>2025-10-01T17:48:02Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/feed/packages/commit/?id=6a13be222004246108b9974babb0297d91a23acd'/>
<id>urn:sha1:6a13be222004246108b9974babb0297d91a23acd</id>
<content type='text'>
acme.sh supports --httpport and --tlsport options to be used
together with --standalone and --alpn modes respectively.

This is useful if we're behind a reverse proxy or smth like that
or if we cannot bind to standard 80 or 443 port for some other
reason.

This change makes listen_port from configuration to be passed as
either --httpport or --tlsport

Signed-off-by: Vladimir Kochnev &lt;hashtable@yandex.ru&gt;
</content>
</entry>
<entry>
<title>acme-acme.sh: declare staging_moved variable</title>
<updated>2025-10-02T11:14:11Z</updated>
<author>
<name>Vladimir Kochnev</name>
</author>
<published>2025-10-01T17:48:02Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/feed/packages/commit/?id=893576cecd09502c222563b05d8cb541bc2be297'/>
<id>urn:sha1:893576cecd09502c222563b05d8cb541bc2be297</id>
<content type='text'>
It's possible that staging_moved variable is undeclared while being
accessed. Lets explicitly declare it.

Signed-off-by: Vladimir Kochnev &lt;hashtable@yandex.ru&gt;
</content>
</entry>
<entry>
<title>acme-acmesh: support TLS-ALPN-01 challenge</title>
<updated>2025-09-26T13:45:56Z</updated>
<author>
<name>Vladimir Kochnev</name>
</author>
<published>2025-09-26T10:59:11Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/feed/packages/commit/?id=25fcb486bc5ae442ee85aa4729a8fb1f5a5a3e3b'/>
<id>urn:sha1:25fcb486bc5ae442ee85aa4729a8fb1f5a5a3e3b</id>
<content type='text'>
This change adds an ability to invoke acme.sh with --alpn option
invoking a TLS-ALPN-01 challenge on the 443 port.

Signed-off-by: Vladimir Kochnev &lt;hashtable@yandex.ru&gt;
</content>
</entry>
<entry>
<title>acme-acmesh: use validation_method option instead of guessing</title>
<updated>2024-03-01T16:01:40Z</updated>
<author>
<name>Sergey Ponomarev</name>
</author>
<published>2024-02-28T20:13:47Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/feed/packages/commit/?id=4bec28b4d16d86cfb6f6f720c61072f5954a9b28'/>
<id>urn:sha1:4bec28b4d16d86cfb6f6f720c61072f5954a9b28</id>
<content type='text'>
The new validation_method option can be: dns, webroot or standalone.
Previously we guessed the challenge type:
1. if the DNS provider is specified then it's dns
2. if standalone=1
3. fallback to webroot

The logic is preserved and if the validation_method wasn't set explicitly we'll guess it in old manner.

Signed-off-by: Sergey Ponomarev &lt;stokito@gmail.com&gt;
</content>
</entry>
<entry>
<title>acme: standardize key_type</title>
<updated>2023-05-18T04:48:47Z</updated>
<author>
<name>Glen Huang</name>
</author>
<published>2023-05-17T09:53:51Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/feed/packages/commit/?id=6d61014e51266f1cb083d9f31491f9c5fb73eeb0'/>
<id>urn:sha1:6d61014e51266f1cb083d9f31491f9c5fb73eeb0</id>
<content type='text'>
keylength, being an acme.sh value type, uses pure numbers for rsa keys.
This can be disorienting for other acme clients. This change introduces
a new option "key_type" that aims to remove this ambiguity, and makes
all key type names follow the same pattern, making acme-common more
client agnostic.

Signed-off-by: Glen Huang &lt;me@glenhuang.com&gt;
</content>
</entry>
</feed>
