From: Denton Liu <liu.denton@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Git Mailing List <git@vger.kernel.org>,
Luis Marsano <luis.marsano@gmail.com>,
Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: [PATCH 0/2] contrib/credential/netrc: Makefile + script cleanup
Date: Mon, 16 Dec 2019 22:17:23 -0800 [thread overview]
Message-ID: <20191217061723.GA507345@generichostname> (raw)
In-Reply-To: <20191217024858.GA2734969@coredump.intra.peff.net>
Hi Peff,
On Mon, Dec 16, 2019 at 09:48:58PM -0500, Jeff King wrote:
> On Mon, Dec 16, 2019 at 01:32:32PM -0800, Denton Liu wrote:
>
> > I recently switched my workflow to use this credential helper and I
> > noticed a couple of problems:
> >
> > 1. The interpreter path was hardcoded to #!/usr/bin/perl
> >
> > 2. The script refuses to run outside of a Git repository
> >
> > This patch series should fix these problems.
>
> Both of these patches look good to me.
Thanks for reviewing :)
>
> It does make me wonder if many people are using credential-netrc, given
> these pretty obvious problems. You're certainly welcome to use it if it
> works for you, but I am curious what made you pick it versus one of the
> other more advanced helpers.
I wanted a credential helper that was encrypted and OS-independent.
Since GPG is basically available on everything, it fits my use case.
It also helped that it resulted in a workflow that was very similar to
my old mutt workflow. Before, I had
source "gpg -dq ~/.mutt/credentials.gpg |"
and I just replaced the gpg with a script that wraps around git-credential.
>
> I assume you're using a gpg-encrypted netrc (if not, you should probably
> just use credential-store). For "read-only" password access, I find the
> combination of pass[1] with config like this is a bit nicer:
Nice, I never knew heard about pass until now. I only have one password
in my credential store currently but if I need to add more, I'll keep
this in mind!
-Denton
>
> [credential "https://github.com"]
> username = peff
> helper = "!f() { test $1 = get && echo password=`pass github/oauth`; }; f"
>
> -Peff
>
> [1] https://www.passwordstore.org/
next prev parent reply other threads:[~2019-12-17 6:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 21:32 [PATCH 0/2] contrib/credential/netrc: Makefile + script cleanup Denton Liu
2019-12-16 21:32 ` [PATCH 1/2] contrib/credential/netrc: make PERL_PATH configurable Denton Liu
2019-12-16 21:32 ` [PATCH 2/2] contrib/credential/netrc: work outside a repo Denton Liu
2019-12-17 2:48 ` [PATCH 0/2] contrib/credential/netrc: Makefile + script cleanup Jeff King
2019-12-17 6:17 ` Denton Liu [this message]
2019-12-20 18:44 ` [RESEND PATCH " Denton Liu
2019-12-20 18:45 ` [RESEND PATCH 1/2] contrib/credential/netrc: make PERL_PATH configurable Denton Liu
2019-12-20 18:45 ` [RESEND PATCH 2/2] contrib/credential/netrc: work outside a repo Denton Liu
2019-12-20 20:59 ` [RESEND PATCH 0/2] contrib/credential/netrc: Makefile + script cleanup 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=20191217061723.GA507345@generichostname \
--to=liu.denton@gmail.com \
--cc=git@vger.kernel.org \
--cc=luis.marsano@gmail.com \
--cc=peff@peff.net \
--cc=tzz@lifelogs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.