git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: git@vger.kernel.org
Cc: Erik Faye-Lund <kusmabite@gmail.com>, Junio C Hamano <gitster@pobox.com>
Subject: [PATCHv2 0/7] getpass refactoring
Date: Thu, 8 Dec 2011 03:21:19 -0500	[thread overview]
Message-ID: <20111208082118.GA1507@sigill.intra.peff.net> (raw)

This is a re-roll of the earlier "echo usernames as they are typed"
series here:

  http://article.gmane.org/gmane.comp.version-control.git/185970

It turns out that getpass() isn't even really good at getting passwords.
See patch 5/7 for details. This series replaces it entirely if you set
HAVE_DEV_TTY (otherwise, we continue to fallback to getpass()).

  [1/7]: imap-send: avoid buffer overflow
  [2/7]: imap-send: don't check return value of git_getpass
  [3/7]: move git_getpass to its own source file
  [4/7]: refactor git_getpass into generic prompt function
  [5/7]: add generic terminal prompt function
  [6/7]: prompt: use git_terminal_prompt
  [7/7]: credential: use git_prompt instead of git_getpass

It should be applied on top of the jk/credentials topic.

-Peff

             reply	other threads:[~2011-12-08  8:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-08  8:21 Jeff King [this message]
2011-12-08  8:23 ` [PATCH 1/7] imap-send: avoid buffer overflow Jeff King
2011-12-08  8:24 ` [PATCH 2/7] imap-send: don't check return value of git_getpass Jeff King
2011-12-08  8:24 ` [PATCH 3/7] move git_getpass to its own source file Jeff King
2011-12-08  8:31 ` [PATCH 4/7] refactor git_getpass into generic prompt function Jeff King
2011-12-09 23:58   ` Junio C Hamano
2011-12-08  8:33 ` [PATCH 5/7] add generic terminal " Jeff King
2011-12-08 21:48   ` Jakub Narebski
2011-12-08 21:52     ` Jeff King
2011-12-08  8:33 ` [PATCH 6/7] prompt: use git_terminal_prompt Jeff King
2011-12-08  8:33 ` [PATCH 7/7] credential: use git_prompt instead of git_getpass Jeff King

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=20111208082118.GA1507@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=kusmabite@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).