From: Brian Cully via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org>
To: Julien Lepiller <julien@lepiller.eu>
Cc: Felix Lechner <felix.lechner@gmail.com>,
Vagrant Cascadian <vagrant@reproducible-builds.org>,
guix-devel@gnu.org
Subject: Re: maradns reproducibility fixes and the merits of picking a random number
Date: Tue, 07 Jun 2022 08:11:54 -0400 [thread overview]
Message-ID: <8735ggfz3v.fsf@ditto.jhoto.spork.org> (raw)
In-Reply-To: <310AD876-916E-4020-A87E-5609E8166432@lepiller.eu>
>>The upstream website says: "People like MaraDNS because it’s ...
>>remarkably secure." [1] Since many distributions have the same
>>issue,
>>upstream could perhaps offer the patch as a build switch to
>>enable a
>>build-time seed only when needed.
>
> Sounds like the safest option. Maybe we could change the code
> that uses that number to naise an exception or abort?
This seems like the best option to me, as well: either add a flag
to explicitly enable embedding a constant, or remove the code
entirely and replace it with a build failure (or runtime failure,
if a build failure is not possible). It seems like a mis-feature
to me to embed a constant seed, and invites silent
misconfiguration which will lead to security breaches.
-bjc
next prev parent reply other threads:[~2022-06-07 12:49 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 1:49 maradns reproducibility fixes and the merits of picking a random number Vagrant Cascadian
2022-06-07 3:24 ` Felix Lechner
2022-06-07 5:20 ` Julien Lepiller
2022-06-07 12:11 ` Brian Cully via Development of GNU Guix and the GNU System distribution. [this message]
2022-06-08 11:48 ` Efraim Flashner
2022-06-08 14:09 ` Tobias Geerinckx-Rice
2022-06-08 11:47 ` Efraim Flashner
2022-06-08 20:33 ` Vagrant Cascadian
2022-06-23 2:05 ` Vagrant Cascadian
2022-06-28 1:31 ` Vagrant Cascadian
2022-06-28 9:30 ` Efraim Flashner
2022-06-28 15:39 ` Jack Hill
2022-06-28 16:04 ` Tobias Geerinckx-Rice
2022-06-28 16:18 ` Gábor Boskovits
2022-06-28 16:33 ` Vagrant Cascadian
2022-06-28 19:06 ` Tobias Geerinckx-Rice
2022-06-28 19:15 ` Tobias Geerinckx-Rice
2022-07-12 2:36 ` Vagrant Cascadian
2022-07-12 2:41 ` Vagrant Cascadian
2022-07-18 11:21 ` Ludovic Courtès
2022-07-19 13:09 ` Tobias Geerinckx-Rice
2022-06-07 15:15 ` Ludovic Courtès
2022-06-08 19:28 ` Arun Isaac
2022-06-08 20:25 ` Vagrant Cascadian
2022-06-14 17:16 ` Philip McGrath
2022-06-08 19:43 ` Liliana Marie Prikler
2022-06-08 20:23 ` Vagrant Cascadian
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8735ggfz3v.fsf@ditto.jhoto.spork.org \
--to=guix-devel@gnu.org \
--cc=bjc@spork.org \
--cc=felix.lechner@gmail.com \
--cc=julien@lepiller.eu \
--cc=vagrant@reproducible-builds.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).