git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frank Li <lznuaa@gmail.com>
To: Eric Wong <normalperson@yhbt.net>
Cc: Laszlo Papp <djszapi@archlinux.us>,
	Tay Ray Chuan <rctay89@gmail.com>,
	git@vger.kernel.org
Subject: Re: Implement --password option for git svn perl script
Date: Tue, 2 Feb 2010 17:18:52 +0800	[thread overview]
Message-ID: <1976ea661002020118n2b86844k47a1064c028f439f@mail.gmail.com> (raw)
In-Reply-To: <20100202090538.GA28437@dcvr.yhbt.net>

> 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...
>

Yes, it is insecure. "--password" seam undocumented.

> 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?
>
> --
> Eric Wong
>

  reply	other threads:[~2010-02-02  9:19 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 [this message]
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
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=1976ea661002020118n2b86844k47a1064c028f439f@mail.gmail.com \
    --to=lznuaa@gmail.com \
    --cc=djszapi@archlinux.us \
    --cc=git@vger.kernel.org \
    --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).