From: Mike Gaffney <mr.gaffo@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] http authentication via prompts
Date: Thu, 05 Mar 2009 09:15:29 -0600 [thread overview]
Message-ID: <49AFEC91.10009@gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0903051149280.6524@intel-tinevez-2-302>
My thought was that if you had a password you didn't care about you could put it in the config.
It does ask you for a password with getpass, It compiles under cygwin, I havent tried it under
windows. However the man page for getpass shows the source so coding up getpass directly isn't a
big deal.
Junio, I'm new to this patch game and using Thunderbird. What's the best way
to wrap the patch?
-Mike
Johannes Schindelin wrote:
> Hi,
>
> Disclaimer: if you are offended by constructive criticism, or likely to
> answer with insults to the comments I offer, please stop reading this mail
> now (and please do not answer my mail, either). :-)
>
> Still with me? Good. Nice to meet you.
>
> Just for the record: responding to a patch is my strongest way of saying
> that I appreciate your work.
>
> On Wed, 4 Mar 2009, Mike Gaffney wrote:
>
>> Currently git over http only works with a .netrc file which required
>> that you store your password on the file system in plaintext. This
>> commit adds to configuration options for http for a username and an
>> optional password. If a http.username is set, then the .netrc file is
>> ignored and the username is used instead. If a http.password is set,
>> then that is used as well, otherwise the user is prompted for their
>> password.
>
> From the subject, I would have expected a way to type in the password
> instead of storing it. (Think getpass()... which would pose problems
> with Windows support, of course.)
>
> FWIW by having it in .git/config (which is most likely more world-readable
> than $HOME/.netrc ever will be) does not provide any security over .netrc.
>
> And I doubt that http.username is a good choice: what if you have multiple
> http:// URLs with different usernames/passwords? So would it not make
> more sense to make this remote.<name>.user and ...password?
>
> Ciao,
> Dscho
--
-Mike Gaffney (http://rdocul.us)
next prev parent reply other threads:[~2009-03-05 15:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-05 1:07 [PATCH] http authentication via prompts Mike Gaffney
2009-03-05 7:34 ` Junio C Hamano
2009-03-05 10:55 ` Johannes Schindelin
2009-03-05 15:15 ` Mike Gaffney [this message]
2009-03-05 16:37 ` Jeff King
2009-03-06 22:52 ` Fredrik Skolmli
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=49AFEC91.10009@gmail.com \
--to=mr.gaffo@gmail.com \
--cc=git@vger.kernel.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.
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 NNTP newsgroup(s).