From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>, Christopher Baines <mail@cbaines.net>
Cc: "Никита Чураев" <lamefun.x0r@gmail.com>, guix-devel@gnu.org
Subject: Re: Idea: Install script to better support improving contributor-friendliness of projects
Date: Tue, 28 Nov 2017 17:11:15 +0100 [thread overview]
Message-ID: <87bmjmxu1o.fsf@gnu.org> (raw)
In-Reply-To: <87bmjook1w.fsf@netris.org> (Mark H. Weaver's message of "Sun, 26 Nov 2017 15:35:07 -0500")
Hello,
Mark H Weaver <mhw@netris.org> skribis:
> Никита Чураев <lamefun.x0r@gmail.com> writes:
>
>> Here's how I want to use Guix and it is to increase
>> contributor-friendliness of a project, so that the user can simply run
>> a distribution-independent command to install all dependencies without
>> having to hunt for them with `apt` and `dnf` manually.
>>
>> Unfortunately, Guix itself is not very easy to install, and the
>> instructions are full of rather technical stuff like 'systemd' and
>> 'upstart'.
>>
>> https://www.gnu.org/software/guix/manual/html_node/Binary-Installation.html
>>
>> There should be a script like the one Haskell Stack uses:
>>
>> |curl -sSL https://get.haskellstack.org/ | sh|
>
> I can understand the appeal of such a convenient approach. However,
> this practice of downloading a script via HTTPS and immediately running
> it as root without inspection puts you at considerable risk. A
> man-in-the-middle with the resources to compromise or bribe *any*
> certificate authority in your trust store (the attacker could choose
> which one) could acquire a fraudulent certificate to impersonate our
> site, and then substitute in a different script than the one we
> provided. Quite a few organizations are capable of such an attack
> today.
>
> Therefore, I believe it would be irresponsible for us to promote this
> style of installation.
Seconded.
> However, if there's sufficient interest, and if we could produce a
> sufficiently robust "auto-install" script, we could perhaps do something
> close to what you suggested. We could provide a script along with a
> GnuPG digital signature. We could ask the user to download the script,
> acquire our signing key, verify the signature on the script, and then
> run the script as root.
I while back Chris Baines and someone else (?) had worked on such a
script, but I’m not sure what happened.
Chris, does that ring a bell?
It would be nice to have it in time for the new release.
Ludo’.
next prev parent reply other threads:[~2017-11-28 16:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-26 11:43 Idea: Install script to better support improving contributor-friendliness of projects Никита Чураев
2017-11-26 18:58 ` ng0
2017-11-26 20:35 ` Mark H Weaver
2017-11-28 16:11 ` Ludovic Courtès [this message]
2017-11-28 17:33 ` myglc2
2017-11-28 19:43 ` lamefun.x0r
2017-11-28 21:34 ` Leo Famulari
2017-11-28 21:56 ` Adonay Felipe Nogueira
2017-11-29 6:08 ` Pjotr Prins
2017-11-29 16:47 ` Ricardo Wurmus
2017-11-30 9:59 ` Ludovic Courtès
2017-11-30 11:58 ` Hartmut Goebel
2017-11-30 12:59 ` Arun Isaac
2017-11-30 13:05 ` Vincent Legoll
2017-11-30 13:14 ` Adonay Felipe Nogueira
2017-11-30 13:52 ` Vincent Legoll
2017-11-30 14:12 ` Hartmut Goebel
2017-11-30 17:01 ` Adonay Felipe Nogueira
2017-11-27 21:06 ` Alex Vong
2017-11-27 21:53 ` Adonay Felipe Nogueira
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=87bmjmxu1o.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=lamefun.x0r@gmail.com \
--cc=mail@cbaines.net \
--cc=mhw@netris.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).