|  | Commit message (Collapse) | Author | Age | Files | 
|---|
| | |  | 
| | 
| 
| 
| 
| | It's an internal flag, but can be useful for authorized_keys(5)
restrictions. | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| | lacme(8): for --config=, --socket=, --config-certs= (and ‘socket’/
‘config-certs’/‘challenge-directory’ configuration options *before*
privilege drop; and for the [accountd] section ‘command’/‘config’
configuration options *after* privilege drop).
lacme-accountd(1): for --config=, --socket= and --privkey= (and
‘socket’/‘privkey’ configuration options).
This also changes the default configuration file location.  lacme(8) and
lacme-accountd(1) now respectively use /etc/lacme/lacme.conf resp.
/etc/lacme/lacme-accountd.conf when running as root, and
$XDG_CONFIG_HOME/lacme/lacme.conf resp. $XDG_CONFIG_HOME/lacme/lacme-accountd.conf
when running as a normal user.  There is no fallback to /etc anymore. | 
| | |  | 
| | 
| 
| 
| | And add a test case for this. | 
| | 
| 
| 
| 
| 
| 
| | configuration file.
One need to use the lacme-accountd(1) configuration file for that
instead. | 
| | 
| 
| 
| 
| 
| 
| 
| | default value.
The previous default, namely /etc/lacme/lacme-accountd.conf, is still
honored when there is the user running lacme doesn't have a
~/.config/lacme/lacme-account.conf configuration file. | 
| | 
| 
| 
| 
| | Using stdin/stdout makes it possible to tunnel the accountd connection
through ssh. | 
| | 
| 
| 
| | This doesn't change the default behavior. | 
| | 
| 
| 
| 
| 
| 
| | This is a breaking change: lacme(8) resp. lacme-accountd(1) no longer
consider ./lacme.conf resp. ./lacme-accountd.conf as default location
for the configuration file.  Doing so has security implications when
running these program from insecure directories. | 
| | |  | 
| | 
| 
| 
| | This is mostly useful for OCSP Must-Staple. | 
| | 
| 
| 
| 
| 
| 
| | Since lacme(8) spawns a builtin webserver by default the change doesn't
affect default configurations.
See https://bugs.debian.org/970800 for the rationale. | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | 
| 
| 
| 
| | Which aliases to `--min-days=-1`, i.e., forces renewal regardless of the
expiration date of existing certificates. | 
| | 
| 
| 
| | configurable. | 
| | |  | 
| | 
| 
| 
| 
| | Also, move the most common options ('hash', 'keyUsage', 'CAfile',
'min-days') to the default section. | 
| | |  | 
| | 
| 
| 
| 
| | * Also suggest a command to generate an ECDSA key not just RSA.
 * Hint at which key algorithms are supported. | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| | This is a breaking change.  The certificate indicated by 'CAfile' is no
longer used as is in 'certificate-chain' (along with the leaf cert).
The chain returned by the ACME v2 endpoint is used instead.  This allows
for more flexbility with respect to key/CA rotation, cf.
https://letsencrypt.org/2020/11/06/own-two-feet.html and
https://community.letsencrypt.org/t/beginning-issuance-from-r3/139018
Moreover 'CAfile' now defaults to @@datadir@@/lacme/ca-certificates.crt
which is a concatenation of all known active CA certificates (which
includes the previous default). | 
| | |  | 
| | 
| 
| 
| 
| | This allows remotely-controlled lacme processes being controlled without
modifying an config files.  See https://bugs.debian.org/955767 . | 
| | |  | 
| | |  | 
|  | As it's a system command, see hier(7) for details. |