On 06/09/2021 11:05, Didier 'OdyX' Raboud wrote:
CUPS appears to already have access to everything in /etc/ssl/ on all
systems, which is where I used to keep my CAcert certificates. This doesn't
feel any different.
You're absolutely right; that's convincing to me!
Reopening, and will fix in
Control: reopen -1
Control: tag -1 +pending
Le mercredi, 1 septembre 2021, 22.40:57 h CEST Roger Lynn a écrit :
> On 27/08/2021 14:33, Didier 'OdyX' Raboud wrote:> Control: tags -1 +wontfix
>
> > Using Let's Encrypt is fine, allowed, and (apparently) working with CUPS,
> > but as that's clearly
On 27/08/2021 14:33, Didier 'OdyX' Raboud wrote:> Control: tags -1 +wontfix
Using Let's Encrypt is fine, allowed, and (apparently) working with CUPS,
but as that's clearly not a default way of working for CUPS, I'd be
_very_ reluctant to allow CUPS to access "all the Let's Encrypt
certificates"
Le vendredi, 27 août 2021, 18.31:17 h CEST Roger Lynn a écrit :
> The documentation is definitely lacking - I've been trying to work out why
> my configuration broke since upgrading to Buster 3 months ago! Even with the
> loglevel set to "debug", the logs were utterly unhelpful. Let's Encrypt is
>
The documentation is definitely lacking - I've been trying to work out why
my configuration broke since upgrading to Buster 3 months ago! Even with the
loglevel set to "debug", the logs were utterly unhelpful. Let's Encrypt is
the most popular source of signed certificates and the upstream
Package: cups-daemon
Version: 2.3.3op2-3+deb11u1
Severity: normal
File: /etc/apparmor.d/usr.sbin.cupsd
Adding
/etc/letsencrypt/archive/** r,
seems to fix this.
I only discovered what was causing the problem when I stumbled across
https://askubuntu.com/questions/1079957
Thanks,
Roger
--
6 matches
Mail list logo
