all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: 52690@debbugs.gnu.org
Subject: [bug#52690] Remove direct dependencies on the nss-certs certificate store
Date: Mon, 20 Dec 2021 19:36:31 -0500	[thread overview]
Message-ID: <YcEhjz3Fm6ekOXhs@jasmine.lan> (raw)

[-- Attachment #1: Type: text/plain, Size: 750 bytes --]

Three packages depend directly on nss-certs: ldns, pypy3, and icedtea6.

This is a problem because certificates expire. When that happens, the
features of these programs that use X.509 certificates will stop
working. Instead, packages should look up certificates at run-time in
unversioned and well-known locations such as /etc/ssl/certs or via
environment variables like $SSL_CERT_DIR.

I'll send a patch removing the dependency from ldns.

pypy3 does not build anyways because its runpath cannot be successfully
validated, but I will investigate anyways after disabling the runpath
validator.

Icedtea6 is a very complex package. I assume it depends on the
certificates directly for a good reason, but I would still appreciate
some feedback on it.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2021-12-21  0:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-21  0:36 Leo Famulari [this message]
2021-12-21  0:37 ` [bug#52690] [PATCH] gnu: ldns: Do not depend directly on nss-certs Leo Famulari
2021-12-21  2:48 ` [bug#52690] [PATCH] gnu: pypy3: Prohibit references to nss-certs Leo Famulari
2021-12-26 17:37 ` [bug#52690] Remove direct dependencies on the nss-certs certificate store Mathieu Othacehe
2021-12-26 20:55   ` Leo Famulari
2021-12-26 21:32 ` [bug#52690] [PATCH] gnu: IcedTea: Prohibit references to nss-certs Leo Famulari

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=YcEhjz3Fm6ekOXhs@jasmine.lan \
    --to=leo@famulari.name \
    --cc=52690@debbugs.gnu.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.