From: Steve Diver <squelch2@googlemail.com>
To: Eric Wong <normalperson@yhbt.net>
Cc: Laszlo Papp <djszapi@archlinux.us>, Frank Li <lznuaa@gmail.com>,
Tay Ray Chuan <rctay89@gmail.com>,
git@vger.kernel.org
Subject: Re: Implement --password option for git svn perl script
Date: Fri, 05 Feb 2010 23:01:15 +0000 [thread overview]
Message-ID: <4B6CA33B.8050200@googlemail.com> (raw)
In-Reply-To: <20100202090538.GA28437@dcvr.yhbt.net>
On 02/02/2010 09:05, Eric Wong wrote:
>
> Laszlo Papp<djszapi@archlinux.us> wrote:
>>> The basic requirement is git svn can provide a way to prompt a dialog
>>> box to input passwd.
>>
>> Yeah, it's a very basic use case, but I don't know whether there is a
>> workaround for it somehow, maybe perl gurus or git svn users could
>> help more...
>>
>> My company, where there are windows users (95% of the company), would
>> like to use TortoiseGIT as a graphical client for SVN server
>> repositories as an SVN client, no other way by us, so it'd be high
>> priority :) So I've got a beer for any volunteer, thanks :P
>
> Hi, (fixed subject so I don't mistake it for junk again)
>
> I don't know (and have no way to test) how to deal with input dialogs
> for reading a password on Windows (nor any sort of IPC). Somebody else
> will have to implement it.
>
> Having a --password option in the command line could work, but it's
> painfully insecure if there's any way for another regular user to view
> the process table. Not something I'd like to encourage...
>
> Since SVN already caches passwords in a mostly secure location on disk
> (at least on *nix), shouldn't git svn be able to use the password cache
> SVN uses?
>
Tortoise, along with at least one other Windows GUI utilizes the Putty
suite as a helper app for key chain and password handling, and needs to
be loaded prior to any SSH operations. Tortoise have gone so far as to
rewrite plink (Tortoiseplink.exe)so that that a prompt for the password
is given, but this is undocumented AFAIK.
Otherwise, it is an unfortunate fact that a DOS console session is
invoked whenever openSSH is used. For the average Windows user this is a
scary occurrence, and is one of the obstacles that prevents wider casual
take up of Git on Windows IMHO.
I understand that it comes down to a problem with communication between
a dialogue and an SSH client via STDOUT. I believe Dscho might have some
insight into this as it is a recurrent topic on the MsysGit tracker.
Steve
next prev parent reply other threads:[~2010-02-05 23:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-29 14:17 Implement --password option for git svn perl script Laszlo Papp
[not found] ` <001636ed7681994278047e4e4a6f@google.com>
2010-01-29 14:18 ` Fwd: Delivery Status Notification (Failure) Laszlo Papp
2010-01-29 15:04 ` Frank Li
2010-02-01 16:16 ` Laszlo Papp
2010-02-02 4:15 ` Tay Ray Chuan
2010-02-02 4:30 ` Frank Li
2010-02-02 6:37 ` Laszlo Papp
2010-02-02 9:05 ` Implement --password option for git svn perl script Eric Wong
2010-02-02 9:18 ` Frank Li
2010-02-02 13:16 ` Laszlo Papp
2010-02-02 23:47 ` Frank Li
2010-02-04 7:45 ` Laszlo Papp
2010-02-05 23:01 ` Steve Diver [this message]
2010-02-08 6:29 ` Laszlo Papp
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=4B6CA33B.8050200@googlemail.com \
--to=squelch2@googlemail.com \
--cc=djszapi@archlinux.us \
--cc=git@vger.kernel.org \
--cc=lznuaa@gmail.com \
--cc=normalperson@yhbt.net \
--cc=rctay89@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.
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).