From: "Shawn O. Pearce" <spearce@spearce.org>
To: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
Cc: Marek Zawirski <marek.zawirski@gmail.com>, git@vger.kernel.org
Subject: Re: [JGIT RFC PATCH] Add a stdio prompt for SSH connection information.
Date: Sun, 22 Jun 2008 19:13:55 -0400 [thread overview]
Message-ID: <20080622231355.GH11793@spearce.org> (raw)
In-Reply-To: <200806222306.25434.robin.rosenberg.lists@dewire.com>
Robin Rosenberg <robin.rosenberg.lists@dewire.com> wrote:
> Starting a command line utility like jgit and getting a graphical prompt is almost
> an insult. The problem here is that Java 5, which we support, does not have a
> portable way of disabling echoing of characters. Java 6 (and anythung newr)
> does. There are several solutions involving non-portable tricks. Should we
> support an insecure practice of echoing passwords, or as I do here, only support
> it if one is using Java 6. A downside of supporting it at all is that one needs a
> JavaSE 6 compiler to build the thing.
We really shouldn't support insecure entry of the password. But I'm
also not ready to give up on Java 5 support either. I wonder if
we shouldn't hide the console reading/writing into a class in our
util package and use reflection to access it, like we do for the
executable flag of java.io.File.
> btw, does anyone know if console() yields null when runnings as a Windows
> service? I tentatively assume that it does without explicily setting the headless
> property.
I think that services on Windows have no console, and also can't
talk to the desktop UI, so its both headless and without a console.
> I'm also a little unsure about how to invoke the promptKeyboardInteractive method.
I think you implemented this method correctly. Its a confusing API,
but it does seem to make sense.
--
Shawn.
next prev parent reply other threads:[~2008-06-22 23:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-22 21:06 [JGIT RFC PATCH] Add a stdio prompt for SSH connection information Robin Rosenberg
2008-06-22 23:13 ` Shawn O. Pearce [this message]
2008-06-23 6:23 ` Robin Rosenberg
2008-06-23 6:34 ` Shawn O. Pearce
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=20080622231355.GH11793@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=marek.zawirski@gmail.com \
--cc=robin.rosenberg.lists@dewire.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