all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: 31284@debbugs.gnu.org
Subject: bug#31284: [PATCH 0/1] guix: Add git-fetch/impure.
Date: Sun, 29 Apr 2018 13:28:13 -0400	[thread overview]
Message-ID: <87vac9ylaq.fsf@netris.org> (raw)
In-Reply-To: <87o9i4szg8.fsf@gmail.com> (Chris Marusich's message of "Fri, 27 Apr 2018 21:54:31 -0700")

Hi Chris,

Chris Marusich <cmmarusich@gmail.com> writes:

> You've both said that you would prefer not to add git-fetch/impure to
> Guix.  Can you help me to understand why you feel that way?  I really
> think it would be nice if Guix could fetch Git repositories over SSH
> using public key authentication, so I'm hoping that we can talk about it
> and figure out an acceptable way to implement it.

I thought about it some more, and found that I cannot really justify my
position on this, so I hereby drop my objection.  It's obviously not
useful for packages that will be included in Guix itself, which is our
primary focus, but I suppose it could be useful for private package
definitions.

What do you think, David?  It seems to me that password tokens in URLs
raise possible security risks, whereas public-key authentication is
generally better practice.

       Mark

       reply	other threads:[~2018-04-29 17:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87o9i4szg8.fsf@gmail.com>
2018-04-29 17:28 ` Mark H Weaver [this message]
2018-04-30 13:59   ` bug#31284: [PATCH 0/1] guix: Add git-fetch/impure Thompson, David
2018-04-27  8:12 Chris Marusich
2018-04-27 13:05 ` Thompson, David
2018-04-28  4:45   ` Chris Marusich
2018-04-29 17:21     ` Ludovic Courtès
2018-04-27 21:37 ` Mark H Weaver
2018-04-29 17:39 ` Mark H Weaver
2018-04-30  0:18   ` Chris Marusich

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=87vac9ylaq.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=31284@debbugs.gnu.org \
    --cc=cmmarusich@gmail.com \
    /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.