Re: Https password present in git output

On Thu, Jul 14, 2016 at 01:36:52AM +0300, ervion wrote: > It is in fact the case, that git fetch output is scrubbed, sorry I did not > notice previously. > But (on my device: git version 2.9.0 arch linux) git push is not. > $ git push origin --all Maybe this? -- >8 -- Subject: [PATCH] push:

Re: Https password present in git output

I completely agree that it is not a head-on-fire kind of problem, there are ways to avoid it. Simply nice to have. It is in fact the case, that git fetch output is scrubbed, sorry I did not notice previously. But (on my device: git version 2.9.0 arch linux) git push is not. $ git push

Re: Https password present in git output

On wo, 2016-07-13 at 20:26 +0300, ervion wrote: > One possibility for this in git is to save remote in the  > https://username:passw...@domain.com/repo.git format. This is not recommended. Git has credential helpers to help you store passwords outside the git configuration. Which then makes your

Re: Https password present in git output

On Wed, Jul 13, 2016 at 11:09 AM, Junio C Hamano wrote: > ervion writes: > >> 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 >>

Re: Https password present in git output

ervion writes: > 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

Https password present in git output

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