From mboxrd@z Thu Jan 1 00:00:00 1970 From: Roel Janssen Subject: Re: What's next? Date: Mon, 29 May 2017 00:05:23 +0200 Message-ID: <87k2501vto.fsf@gnu.org> References: <877f16z9eo.fsf@gnu.org> <874lwaql17.fsf@gnu.org> <20170524214539.GA26320@jasmine> <20170525081130.GA3521@thebird.nl> <87vaomtxiq.fsf@gnu.org> <20170528073057.GA12848@thebird.nl> <877f10oggw.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:41154) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dF6Jf-0006lh-0W for guix-devel@gnu.org; Sun, 28 May 2017 18:05:40 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dF6Jd-0005eB-Tl for guix-devel@gnu.org; Sun, 28 May 2017 18:05:39 -0400 In-reply-to: <877f10oggw.fsf@gnu.org> 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+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Ludovic =?utf-8?Q?Court=C3=A8s?= Cc: guix-devel Ludovic Courtès writes: > Pjotr Prins skribis: > >> On Sat, May 27, 2017 at 12:16:45PM +0200, Ludovic Court??s wrote: >>> On GuixSD, the key of hydra.gnu.org and bayfront.guixsd.org are always >>> registered by default. We cannot do that for someone installing Guix on >>> a foreign distro because that involves creating a file in /etc. >> >> Many installs are not on GuixSD. Can't we use the key that is stored >> in the store itself? If /etc does not exist then use what comes >> with the installation. > > The current behavior is to print a warning when /etc/guix/acl (the list > of authorized keys) is empty or nonexistent. > > Your suggestion would be to automatically populate it, right? > > I’m mildly reluctant to that, because we’d stealthily force every user > into trusting our substitute servers. OTOH I agree that the current > situation is not optimal. > > What do people think? Maybe we could find a mid-way here by doing the same as Fedora does with RPMfusion repositories: It asks the user for trusting the signing keys before enabling the repository. So in our case it would be something like: $ guix package -i emacs A `substitute' is available for this package on https://mirror.hydra.gnu.org. This means we can download the binary output for this package, instead of compiling it from its source code. Do you want to use this substitute server with key ... for this package, and for future packages? [y/N] We need to find the proper wording for this message. Using this, we can still let the user decide, but we can make it a lot easier for the user to make a decision -- a 'yes' or 'no' answer to a question is easier than a paragraph in the manual with instructions to enable it. Kind regards, Roel Janssen