git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: ervion <ervion@cryptolab.net>
To: git@vger.kernel.org
Subject: Https password present in git output
Date: Wed, 13 Jul 2016 20:26:27 +0300	[thread overview]
Message-ID: <2908abd39c722c080ec37a987a79e32f@cryptolab.net> (raw)


Sometimes using ssh is not possible and saving https password in plain 
text to disk may be desireable
(in case of encrypted disk it would be equivalent security with caching 
password in memory).

One possibility for this in git is to save remote in the 
https://username:password@domain.com/repo.git format.
However, in this case every time you push or pull, the remote address, 
including the plain text password.
That would introduce additional security issiues and is unreasonable?

Wouldn't it make sense to scrabble the password part in remote's url 
before printing it to output?

             reply	other threads:[~2016-07-13 17:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-13 17:26 ervion [this message]
2016-07-13 18:09 ` Https password present in git output Junio C Hamano
2016-07-13 18:16   ` Junio C Hamano
2016-07-13 22:36     ` ervion
2016-07-13 23:36       ` Jeff King
2016-07-13 18:16 ` Dennis Kaarsemaker

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=2908abd39c722c080ec37a987a79e32f@cryptolab.net \
    --to=ervion@cryptolab.net \
    --cc=git@vger.kernel.org \
    /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).