From: Jack Hill <jackhill@jackhill.us>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: Vagrant Cascadian <vagrant@reproducible-builds.org>,
Julien Lepiller <julien@lepiller.eu>,
guix-devel@gnu.org, Felix Lechner <felix.lechner@gmail.com>
Subject: Re: maradns reproducibility fixes and the merits of picking a random number
Date: Tue, 28 Jun 2022 11:39:47 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.21.2206281137480.14634@marsh.hcoop.net> (raw)
In-Reply-To: <YrrKMjNsCuSmOgFZ@3900XT>
[-- Attachment #1: Type: text/plain, Size: 1464 bytes --]
On Tue, 28 Jun 2022, Efraim Flashner wrote:
> On Mon, Jun 27, 2022 at 06:31:41PM -0700, Vagrant Cascadian wrote:
>>>
>>> https://github.com/samboy/MaraDNS/discussions/101#discussioncomment-3006487
>>
>> Upstream appears to think it is mostly ok to actually embed a specific
>> random prime... and not have it be different across all the builds, as
>> the number is mixed with other randomness from /dev/urandom.
>>
>> It is expensive to generate the random prime on some hardware, so doing
>> so at runtime might not be feasible in some cases...
>>
>> So, where do we go from here, knowing what we now know? :)
>>
>>
>> live well,
>> vagrant
>
> I looked back at the original email. I think we should not embed a
> static random prime and mark it as non-substitutable. Then with that
> flag add a note that it generates a prime during building and everyone
> having a unique prime is more important to us than everyone having the
> same reproducible prime.
Hi, I think I lost something in the reasoning here. It sounded to me like
upstream was OK with embedding a fixed prime, and even suggested one:
> If one’s coding style can’t have a random 32-bit number in a build, make
> MUL_CONSTANT an unchanging number like 1748294267 (the number I use for
> Windows builds of Deadwood). Deadwood will still be secure from hash
> bucket collision attacks except in the very rare corner case of
> /dev/urandom not giving out good random numbers.
Best,
Jack
next prev parent reply other threads:[~2022-06-28 15:40 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.
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 [this message]
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=alpine.DEB.2.21.2206281137480.14634@marsh.hcoop.net \
--to=jackhill@jackhill.us \
--cc=efraim@flashner.co.il \
--cc=felix.lechner@gmail.com \
--cc=guix-devel@gnu.org \
--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).