#22883 - Trustable "guix pull" - GNU bug report logs

Package	Source(s)		Maintainer(s)
guix		PTS Buildd Popcon

Message #216 received at 22883@debbugs.gnu.org (full text, mbox, reply):

Received: (at 22883) by debbugs.gnu.org; 2 Jun 2020 23:45:31 +0000
From debbugs-submit-bounces@debbugs.gnu.org Tue Jun 02 19:45:31 2020
Received: from localhost ([127.0.0.1]:41309 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces@debbugs.gnu.org>)
	id 1jgGb5-0001nt-Bg
	for submit@debbugs.gnu.org; Tue, 02 Jun 2020 19:45:31 -0400
Received: from mail-qv1-f54.google.com ([209.85.219.54]:37658)
 by debbugs.gnu.org with esmtp (Exim 4.84_2)
 (envelope-from <zimon.toutoune@gmail.com>) id 1jgGb4-0001nh-K7
 for 22883@debbugs.gnu.org; Tue, 02 Jun 2020 19:45:30 -0400
Received: by mail-qv1-f54.google.com with SMTP id y9so238613qvs.4
 for <22883@debbugs.gnu.org>; Tue, 02 Jun 2020 16:45:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
 h=mime-version:references:in-reply-to:from:date:message-id:subject:to
 :cc:content-transfer-encoding;
 bh=tyAw0+LGCV5qfNKzwXlT2ouBq0RLVOujzVumYlXVBx8=;
 b=ZZV3JgBJgKNsD7wXTqDUkiQ38pn7/nm4TvbYFr+gEl4gO/mHBD7worN/pWjp6owNmV
 +7Pn0+8K/CNFqu2nch7FQH/Tq8LUWc9Hadjo4iZGl3hQVpsmz6Tf+JBU1hrtTcEwb4IR
 drD8ZDD7M0CNOfGKkMF9KzIONbhxDdV1i/mQNy6qsuQbts7pgT8mUmzwfLtBwSLenx1S
 xC/jTCoyZMaoACKKtLoIbyfR4/2xWV3KbCcVZAjFO1eYpxv9SCkCH2IGCJZp0p4O/hX0
 WSWg98o7xlA+ZMaW52MgCViNQ0UeOnbf71sNAO07b2aGwSCA4iwgScUuro3ATWHGhZhh
 /Aig==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:mime-version:references:in-reply-to:from:date
 :message-id:subject:to:cc:content-transfer-encoding;
 bh=tyAw0+LGCV5qfNKzwXlT2ouBq0RLVOujzVumYlXVBx8=;
 b=DaxDUFbI0NwKpjZpPYKY+7cxhYCBCTm3BmFljV6F7NT2NT/oL8ziMgl505tU7qKh4N
 p4DwNQYV3QsiTtEyu511hVdz1M+OZSPXrt7wQN/QjyayuN2sOdhPZb1/8S6/di+hBH21
 jY0DTJTWwdFSkJ0m3GwghAQMwuKU/5GKd2vH7Ybk82u+R+xiYf6knG27GFSWwzs1ziBl
 Q8i0Cm9AapCeqSTZEBs0dJO5vtHCqG3f06owHjHtOwYDfqSi8pCgRNcG3ycKDskJDw6a
 qIHJB/78+5dxXLg3QfAMXw8VDbjl0+X5AMua2jaoAG/661kRUXtHGZAAOJAWU12W2Twl
 hv1w==
X-Gm-Message-State: AOAM532Fn2QQzAa/0E5egqUENhkJ66UeNVc+/o8o2QpkOaLwGE1IoOqP
 qyVq2yyjPp1w6W/I4fJO+erJ1Xc73s/KgIbP5ss=
X-Google-Smtp-Source: ABdhPJyqs4l+pf8AxM5y64VizTa10WIupb+OKK1r++P2dZWR3UJdAlEMKwtOmfIfIQF336LtWhFsECLq17Zgq9nM8KU=
X-Received: by 2002:ad4:536a:: with SMTP id e10mr7860291qvv.246.1591141524892; 
 Tue, 02 Jun 2020 16:45:24 -0700 (PDT)
MIME-Version: 1.0
References: <87io14sqoa.fsf@dustycloud.org> <87h9ep8gxk.fsf@gnu.org>
 <20160426001359.GA23088@jasmine> <874majg0z8.fsf@gnu.org>
 <87bn3iz1xc.fsf_-_@gnu.org>
 <87wpket748.fsf@gnu.org> <87bmkwm8ed.fsf@gnu.org> <87png9o8i2.fsf@elephly.net>
 <87fth4bj6y.fsf@gnu.org> <87bln9oupo.fsf@gnu.org> <87wo5vfuxi.fsf@gnu.org>
 <87o8qjekt7.fsf@gnu.org> <87v9kanalz.fsf_-_@gnu.org>
In-Reply-To: <87v9kanalz.fsf_-_@gnu.org>
From: zimoun <zimon.toutoune@gmail.com>
Date: Wed, 3 Jun 2020 01:45:13 +0200
Message-ID: <CAJ3okZ197ip5HG8P66tVhtNiTcxBv63yfWk7LMeYy=A-Vx2d-Q@mail.gmail.com>
Subject: Re: bug#22883: Channel introductions
To: Ludovic Courtès <ludo@gnu.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Debbugs-Envelope-To: 22883
Cc: 22883@debbugs.gnu.org
X-BeenThere: debbugs-submit@debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request@debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit@debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request@debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request@debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces@debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
X-Spam-Score: -1.0 (-)

Hi Ludo,

Really cool!
Well, even if I am not enough clever to understand all that.

On Mon, 1 Jun 2020 at 16:08, Ludovic Courtès <ludo@gnu.org> wrote:

> I think we need a way to “introduce” a channel to its users that goes
> beyond a mere URL.

Just to be sure to well understand, will the good ol'
~/.config/guix/channels.scm

--8<---------------cut here---------------start------------->8---
     ;; Tell 'guix pull' to use my own repo.
     (list (channel
             (name 'guix)
             (url "https://example.org/my-guix.git")
             (branch "super-hacks")))
--8<---------------cut here---------------end--------------->8---

still work as it is now? i.e., using the current "unauthorized"
mechanism.  Or will a new keyword be added to this channel description
to say "this channel does not use authorized machinery but it is
fine"?

>      If that information were stored in ‘.guix-channel’, it would be
>      trivial for an attacker to fork the project (or push a new commit)
>      and pretend the authentication process must not take previous
>      commits into account.

What will happen to recursive '.guix-channel'?  The '.guix-channel' of
channel A contains the reference to the channel B where the
'.guix-channel' contains the reference to the channel C, etc.

>   4. When publishing a fork of a channel, one emits a new channel
>      introduction.  Users switching to the fork have to explicitly allow
>      that new channel via its introduction; flipping the URL won’t be
>      enough because ‘guix pull’ would report unauthorized commits.

I am a bit afraid by this... and I hope that a fork of a channel will
still work without emitting a new channel introduction.

>   5. The channel URL is not included in the introduction.  However, the
>      official URL is an important piece of information: it tells users
>      this is where they’ll get the latest updates.  It should be
>      possible to create mirrors, but by default users should go to the
>      official URL.  They should be aware that mirrors can be outdated.

I do not understand this paragraph.  The aim of mirrors is to avoid
the users to go to the official URL, isn't it?  And the mirrors do not
have by design the latest updates (time to propagate, etc.).

>      I think the official URL can be stored in ‘.guix-channel’ in the
>      repo (which is subject to the authentication machinery).  That way,
>      ‘guix pull’ can let the user know if they’re talking to a mirror
>      rather than to the official channel.

Why does it matter?  The user should authenticate the downloaded
content whatever the URL serving it, isn't it?
And can 'guix pull' already let the users know to who they are talking?

> This verbose interface creates an incentive to create a ‘guix channel’
> command that could make it easier to add a new channel.

Yahoga! :-)

Thank you.

All the best,
simon

Display info messages

Send a report that this bug log contains spam.

debbugs.gnu.org maintainers <help-debbugs@gnu.org>. Last modified: Sun Dec 22 01:37:48 2024; Machine Name: wallace-server

GNU bug tracking system

Debbugs is free software and licensed under the terms of the GNU Public License version 2. The current version can be obtained from https://bugs.debian.org/debbugs-source/.

#22883 Trustable "guix pull"