From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: cups: add support for gnutls to enable https
Date: Sat, 25 Feb 2023 03:01:20 +0100 [thread overview]
Message-ID: <20230225020120.1N22KijxUXXTqwm7_vgq68PJRdylbLQzCdO8Bj9PxH0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40467@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 959 bytes --]
There's a closed pull request on the void-packages repository
cups: add support for gnutls to enable https
https://github.com/void-linux/void-packages/pull/40467
Description:
Without gnutls CUPS defaults to the MacOS path for certificates. https://github.com/OpenPrinting/cups/blob/19047059/scheduler/conf.c#L607-L612
When administering printers in CUPS UI (localhost:631) I noticed that the connection could not upgrade to HTTPS. Upon investigation with `strace` I saw that CUPS was trying to load certificates from `/Library/Keychains/System.keychain`.
```
openat(AT_FDCWD, "/Library/Keychains/System.keychain/void.key", O_WRONLY|O_CREAT|O_TRUNC, 0666) = -1 ENOENT (No such file or directory)
```
Enabling GNUTLS causes CUPS to look in the correct location for certificates.
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-GLIBC)
prev parent reply other threads:[~2023-02-25 2:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 13:18 [PR PATCH] " tsndqst
2023-02-10 2:40 ` github-actions
2023-02-25 2:01 ` github-actions [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230225020120.1N22KijxUXXTqwm7_vgq68PJRdylbLQzCdO8Bj9PxH0@z \
--to=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).