From: Junio C Hamano <gitster@pobox.com>
To: Michael Haggerty <mhagger@alum.mit.edu>
Cc: "Jeff King" <peff@peff.net>,
"Toralf Förster" <toralf.foerster@gmx.de>,
git@vger.kernel.org
Subject: Re: RFC: "git config -l" should not expose sensitive information
Date: Thu, 20 Dec 2012 10:49:52 -0800 [thread overview]
Message-ID: <7vbodo5zjj.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <50D33409.1050309@alum.mit.edu> (Michael Haggerty's message of "Thu, 20 Dec 2012 16:51:37 +0100")
Michael Haggerty <mhagger@alum.mit.edu> writes:
> I think the problem is yet another step earlier: why do we build tools
> that encourage people to store passwords in plaintext in a configuration
> file that is by default world-readable?
True. This particular one mentioned in the thread predates
credential helpers, so it is not faire to say "encourage".
We didn't and we don't.
Care to do a patch to deprecate sendemail.smtppass (i.e. give
warnings to users when it is used) and perhaps replace it with
something based on the credential store or something?
next prev parent reply other threads:[~2012-12-20 18:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-17 11:35 RFC: "git config -l" should not expose sensitive information Toralf Förster
2012-12-20 15:04 ` Jeff King
2012-12-20 15:49 ` Aaron Schrab
2012-12-20 15:52 ` Jeff King
2012-12-20 18:37 ` Junio C Hamano
2012-12-20 16:20 ` Toralf Förster
2012-12-20 15:51 ` Michael Haggerty
2012-12-20 15:54 ` Jeff King
2012-12-20 18:49 ` Junio C Hamano [this message]
2012-12-20 22:31 ` Andrew Ardill
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vbodo5zjj.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=mhagger@alum.mit.edu \
--cc=peff@peff.net \
--cc=toralf.foerster@gmx.de \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).