From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp0.migadu.com ([2001:41d0:303:e224::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms8.migadu.com with LMTPS id cJ/zLiLeB2YjRwEAqHPOHw:P1 (envelope-from ) for ; Sat, 30 Mar 2024 10:40:50 +0100 Received: from aspmx1.migadu.com ([2001:41d0:303:e224::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp0.migadu.com with LMTPS id cJ/zLiLeB2YjRwEAqHPOHw (envelope-from ) for ; Sat, 30 Mar 2024 10:40:50 +0100 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20230601 header.b=NccKQI27; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (aspmx1.migadu.com: domain of "guix-devel-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-devel-bounces+larch=yhetil.org@gnu.org" ARC-Seal: i=1; s=key1; d=yhetil.org; t=1711791650; a=rsa-sha256; cv=none; b=eAHi4WrmKILVl3z5skkMYfdlbsiKjMuTUbZvxdc0JKgONQDYbBNoIvXZkmp6jQVk/fiWq9 31IwVLsLUwH0oNkgEmacoq412+POElIYNaa70a5+VIPaZksZFbSxN5tGrijND/nqzBKYDY 4QZHPgFvGjVOo/yMejbb8un1qxkL/KDsYZurnDHndk4/i0HAlNj0OaXV91Bj6/VkR9FEBK VUp+0itaTvqExr4p7QJ+pDPUMMMfWKObyQU0qVNVpp9NNXkiDSUvVgQyhHIOxYsLP+PVLd kI566geXS6yvUKQO5m0qY1kCsnXI8M/8ctb/da5p7R09Aspz9PG9FmUR/g+v7w== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20230601 header.b=NccKQI27; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (aspmx1.migadu.com: domain of "guix-devel-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-devel-bounces+larch=yhetil.org@gnu.org" ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1711791650; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=/xz3xlJTESdVBhhsJ/TWRcemfPWbdfOBhK252QPDQeE=; b=nUJWcV/2y55JWXwMwOT6jLbbERx1+bss4Vs6TvQDWq5lrCs6CA2huxDDS1cnn5C5s1QSyL lNQLmTMoxhwu5Yi5E7sWevLW6N3yfKVBlvSYhUpohmL+L4mbEmk9hKNhDEINwHlQc3HyYJ kN0pza+8sGCywvzEUecAHczXdCXbj6p63M+pm3+qjeXZag4KyTNbuL5LAphF3NOGdbEj3Q fO4hmadiJmD2DfV6Y8EOmuv1uynp20p/Up5QkACFC36+/zMRspPDkHyiHrkWY97N1FxyYi MV58ZIOq+AcbMt2E7mw3i+DCwBjBQT16h8BANxxTi461FvkqGB4SjEezozRK4w== Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 4772517608 for ; Sat, 30 Mar 2024 10:40:50 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rqVCI-0007mt-Iz; Sat, 30 Mar 2024 05:40:22 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rq3LO-0001rR-8H for guix-devel@gnu.org; Thu, 28 Mar 2024 23:55:54 -0400 Received: from mail-lf1-x12a.google.com ([2a00:1450:4864:20::12a]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1rq3LM-0008Uz-Gp for guix-devel@gnu.org; Thu, 28 Mar 2024 23:55:54 -0400 Received: by mail-lf1-x12a.google.com with SMTP id 2adb3069b0e04-513e25afabaso1762903e87.2 for ; Thu, 28 Mar 2024 20:55:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1711684550; x=1712289350; darn=gnu.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=/xz3xlJTESdVBhhsJ/TWRcemfPWbdfOBhK252QPDQeE=; b=NccKQI27ngQcvtXvjX9XXmQpT2xNkrIiB1F26lnT4V+5ah3RPknecqbmEbDRitH3bp oo44JQAYyofSWA4MX3vKUDs08y5ZJY77gVuZfLv0Kv28Zpi3j/s7aOLyO71w4/jhFLBw hJXPlrfKod2kaiRRqGgtolFZ0DObTtg3JnMQu8m5lO39O8XK7LzlwsdOTX5bgMc5me/i n5IFMXlIOBRNjPMK6hJiBIRbm+8o6a8s7yiRHeUmJffkbm9qoqgEYtKoan6a/3bhN0wI cRwq1Igf3ohTL4hUP9k66b903jojR+R91jAOdmF/djiL/qUsfTxD4pr07oabm/5cwJNe bnbA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1711684550; x=1712289350; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=/xz3xlJTESdVBhhsJ/TWRcemfPWbdfOBhK252QPDQeE=; b=OalOHDgyduoYEhF20uSlgCEWUIla9fx0Tpd/T9dgoGxFpQhCDic7XZAzgqZskXKeyz wAa+pbkQy5MQ9p3ZXR1ncCC9JK4UUIIteMgooigIeu6E5hRcVBImhWW1oi2dv4BgipTV e1V3NzLbqPAaqhSWRgdMhLvNs6X+5lCV9jqgZRJWIlcDyw1ugmPnV5VKwUCHw1s8cmx9 7lnTYagHKvhJUhy6UonZ/qW1wLR868SmiMHkEIHHTk/VYdd70kZQkwsPWiexGwgHLmhL JrKTkKEKrgO8vt5ZU3i8u6BmPD5gzI24Ux6uZrWhYstYhrlWTXcYEa8NQ9YHGj3fc9Np BA6g== X-Gm-Message-State: AOJu0Yz8+D730npuD1bpXCxp9SdQ99kVwzgpHNy4Z4ahV2WdCDqmLw5s ZQcdcSdl9frtN1NAvFIMCCZTE2UE8yfxwJ3Ufp2Snd3DoNpc5yEPuURBa7TFamL2fNYOrR43Tt7 UwrcNdDONNQc2wjxWcLNPpMuh194= X-Google-Smtp-Source: AGHT+IFA2AQ+ClIs8utqy2FHgSh1KgfP8PGGn2i1wEn9y2YKi/0i/JtRpZYqP4Dgmoi9VHXalldkDAez/dyJkzSSXsQ= X-Received: by 2002:ac2:465e:0:b0:515:d100:1650 with SMTP id s30-20020ac2465e000000b00515d1001650mr394383lfo.57.1711684549479; Thu, 28 Mar 2024 20:55:49 -0700 (PDT) MIME-Version: 1.0 References: <3GFY4DFSZPFIH.26YI5TX7T5BW2@wilsonb.com> <87il16j7my.fsf@gnu.org> <2ECJ523SGTEV4.2UB8BK9J3U8GN@wilsonb.com> In-Reply-To: <2ECJ523SGTEV4.2UB8BK9J3U8GN@wilsonb.com> From: Jake Date: Fri, 29 Mar 2024 14:25:38 +1030 Message-ID: Subject: Re: Losing signing keys for custom Guix channel To: elaexuotee@wilsonb.com Cc: guix-devel@gnu.org Content-Type: multipart/alternative; boundary="0000000000008a84e30614c49df5" Received-SPF: pass client-ip=2a00:1450:4864:20::12a; envelope-from=jforst.mailman@gmail.com; helo=mail-lf1-x12a.google.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-Mailman-Approved-At: Sat, 30 Mar 2024 05:40:21 -0400 X-BeenThere: guix-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+larch=yhetil.org@gnu.org Sender: guix-devel-bounces+larch=yhetil.org@gnu.org X-Migadu-Flow: FLOW_IN X-Migadu-Country: US X-Spam-Score: -7.91 X-Migadu-Queue-Id: 4772517608 X-Migadu-Scanner: mx12.migadu.com X-Migadu-Spam-Score: -7.91 X-TUID: 6E4AGbnQMy4Z --0000000000008a84e30614c49df5 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable If commit i adds a new signing key to the channel=E2=80=99s authorisations = file and commit i+1 is signed with that signing key, then commit i+1 can be used in channel intro. You can=E2=80=99t add a signing key to the authorisations in a commit and s= ign that same commit with the new key. Is that issue here? Jake On Fri, 29 Mar 2024 at 2:13=E2=80=AFpm, wrote: > > > from reading about guix authentication I think the new signing key > > > must be first added to the .guix-authoriations file and that commit > > > must signed with the current signing keys before the new signing > > > key can be used. > > > > Yes, it=E2=80=99s likely the problem; the rest of the description you g= ave > > elaexuotee looks fine to me. > > > > (No need to rewrite the history; changing the introduction is enough.) > > > > Ludo=E2=80=99. > > Well, the catch 22 is that I've lost the original key and so can only sig= n > .guix-authorizations with the new one. > > > (No need to rewrite the history; changing the introduction is enough.) > > Without the old key, I'm gathering that a history rewrite is the only way > right > now. Seems like a fresh channel introduction should be enough, but our > current > authorization check appears to look at earlier commits even in that case, > IIUC. > > Maybe forcing history rewrites on key loss is the desired behavior? I'm n= ot > sure. From a client perspective, the only difference is whether or not yo= u > have > to specify --allow-downgrades on the next pull. In either case a channel > intro > update is necessary. > > --0000000000008a84e30614c49df5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
If commit i adds a new signing key to the channel=E2=80= =99s authorisations file and commit i+1 is signed with that signing key, th= en commit i+1 can be used in channel intro.=C2=A0
You can=E2=80=99t add a signing key to the author= isations in a commit and sign that same commit with the new key.=C2=A0 Is t= hat issue here?=C2=A0

Ja= ke

On Fri, 29 Mar 2024 at 2:13=E2=80=AFpm, <elaexuotee@wilsonb.com> wrote:
> > from reading about guix authentication I thi= nk the new signing key
> > must be first added to the .guix-authoriations file and that comm= it
> > must signed with the current signing keys before the new signing<= br> > > key can be used.
>
> Yes, it=E2=80=99s likely the problem; the rest of the description you = gave
> elaexuotee looks fine to me.
>
> (No need to rewrite the history; changing the introduction is enough.)=
>
> Ludo=E2=80=99.

Well, the catch 22 is that I've lost the original key and so can only s= ign
.guix-authorizations with the new one.

> (No need to rewrite the history; changing the introduction is enough.)=

Without the old key, I'm gathering that a history rewrite is the only w= ay right
now. Seems like a fresh channel introduction should be enough, but our curr= ent
authorization check appears to look at earlier commits even in that case, I= IUC.

Maybe forcing history rewrites on key loss is the desired behavior? I'm= not
sure. From a client perspective, the only difference is whether or not you = have
to specify --allow-downgrades on the next pull. In either case a channel in= tro
update is necessary.

--0000000000008a84e30614c49df5--