Git development
 help / color / mirror / Atom feed
From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Jeff King <peff@peff.net>
Cc: Javier.Roucher-Iglesias@ensimag.imag.fr, git@vger.kernel.org,
	Javier Roucher <jroucher@gmail.com>
Subject: Re: [PATCH/RFC] Add 'git credential' plumbing command
Date: Tue, 12 Jun 2012 16:36:03 +0200	[thread overview]
Message-ID: <vpqy5nsppgs.fsf@bauges.imag.fr> (raw)
In-Reply-To: <20120612143411.GA7524@sigill.intra.peff.net> (Jeff King's message of "Tue, 12 Jun 2012 10:34:11 -0400")

Jeff King <peff@peff.net> writes:

> On Tue, Jun 12, 2012 at 04:31:33PM +0200, Matthieu Moy wrote:
>
>> Javier.Roucher-Iglesias@ensimag.imag.fr writes:
>> 
>> > +git credential <fill|approve|reject>
>> 
>> You didn't take Jeff's suggestions into account:
>> 
>> http://thread.gmane.org/gmane.comp.version-control.git/199552/focus=199591
>> 
>> It's clearly too late to implement the whole suggested API, but I do
>> like the suggestion of allowing either a URL as argument or individual
>> fields on stdin, or both combined, by using the --stdin argument.
>> 
>> To allow further patches to implement this without breaking backward
>> compatibility, your implementation could require the use of --stdin on
>> the command-line.
>
> Actually, after further discussion, I think that --stdin is unnecessary.
> If you are providing a URL, you should always provide it via stdin
> because of the password-disclosure issue. It's tempting to provide a
> command-line alternative because it's easier, but I think it would just
> encourage lazy developers to do the wrong thing.

OK, that makes sense.

> I do still think respecting "url=" when reading a credential makes
> sense, but that is easy to add later.

OK, so in short: Javier, you can ignore my comment.

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/

      reply	other threads:[~2012-06-12 14:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-12 14:24 [PATCH/RFC] Add 'git credential' plumbing command Javier.Roucher-Iglesias
2012-06-12 14:31 ` Matthieu Moy
2012-06-12 14:34   ` Jeff King
2012-06-12 14:36     ` Matthieu Moy [this message]

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=vpqy5nsppgs.fsf@bauges.imag.fr \
    --to=matthieu.moy@grenoble-inp.fr \
    --cc=Javier.Roucher-Iglesias@ensimag.imag.fr \
    --cc=git@vger.kernel.org \
    --cc=jroucher@gmail.com \
    --cc=peff@peff.net \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox