all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Christina O'Donnell <cdo@mutix.org>
To: 40316@debbugs.gnu.org
Cc: guix-devel@gnu.org, Steve George <steve@futurile.net>
Subject: Re: nss not reproducible
Date: Thu, 25 Apr 2024 18:01:42 +0100	[thread overview]
Message-ID: <714bd3eb-76ed-2159-9761-f8614a1b164a@mutix.org> (raw)
In-Reply-To: <2dc99b59-cb76-f822-f2ce-027f523bb682@mutix.org>

Hi,

I believe I have a fix for this, I'm just waiting on my machine to hurry 
up and confirm it, might end up running over night, then I'll send my 
patch up.

I'm doing two native builds and two cross-builds.

I've also updated to 3.99.

Kind regards,

Christina

On 25/04/2024 15:06, Christina O'Donnell wrote:
> Hi Steve,
>
>> It would be good to confirm this one:
>>
>> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=40316
>
> Still fails to reproduce with those changes applied.
>
> The culprit is in nss/cmd/shlibsign/shlibsign.c:
>
> shlibSignHMAC generates a new key-pair each time it's run:
>
>     /* Generate a DSA key pair */
>     logIt("Generate an HMAC key ... \n");
>     crv = pFunctionList->C_GenerateKey(hRwSession, &hmacKeyGenMech,
>                                        hmacKeyTemplate,
> PR_ARRAY_SIZE(hmacKeyTemplate),
>                                        &hHMACKey);
>
> Three options:
>  1. Disable library signing entirely.
>  2. Seed the generation to be deterministic.
>  3. Drop in a HMAC key-pair and patch the code to use that instead of 
> generating.
>
> 2 and 3 defeat the point of the cryptographically secure supply chain 
> as the private key can be obtained deterministically, so my vote would 
> be simply  to not sign the libraries (1), which would be easier to 
> maintain. We're not the primary distributor and users can verify our 
> distribution of nss by running `guix challenge` anyway.
>
>> It looks like Zhen Junjie applied two patches to fix NSS 
>> cross-compilation on Master [0]
>
> Building everything cross-compiled to ARM now.
>
> Kind regards,
>
> Christina
>
>


  reply	other threads:[~2024-04-25 17:02 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-24  6:08 Core updates status Steve George
2024-04-24  9:56 ` Christina O'Donnell
2024-04-24 13:17   ` Steve George
2024-04-24 14:21     ` Christina O'Donnell
2024-04-25 14:06     ` Christina O'Donnell
2024-04-25 14:06       ` bug#40316: " Christina O'Donnell
2024-04-25 17:01       ` Christina O'Donnell [this message]
2024-04-25 18:45 ` Kaelyn
2024-04-26 12:56   ` Steve George
2024-04-26 15:58     ` Efraim Flashner
2024-05-05 20:45       ` Josselin Poiret
2024-05-06  2:38         ` Maxim Cournoyer
2024-05-06  8:47           ` Josselin Poiret
2024-05-06 10:21             ` Ludovic Courtès
2024-05-08  9:03               ` Josselin Poiret
2024-05-08 21:42                 ` [PATCH] gnu: glibc: Update patches following upstream's master branch Josselin Poiret
2024-05-14  9:22                   ` Ludovic Courtès
2024-05-09 15:41                 ` Core updates status Maxim Cournoyer
2024-05-13  8:49                 ` Efraim Flashner
2024-05-08 10:05             ` Andreas Enge
2024-05-08 17:46               ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-05-09 15:38               ` Maxim Cournoyer
2024-05-10  8:08                 ` Andreas Enge
2024-05-13  8:51                 ` Efraim Flashner

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=714bd3eb-76ed-2159-9761-f8614a1b164a@mutix.org \
    --to=cdo@mutix.org \
    --cc=40316@debbugs.gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=steve@futurile.net \
    /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.