From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Jeff King <peff@peff.net>
Cc: "BARDOT Jérôme" <bardot.jerome@gmail.com>, git@vger.kernel.org
Subject: Re: Questions, improvements
Date: Wed, 20 Oct 2021 13:42:50 +0200 (CEST) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.2110201340370.56@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <YW85Gs8aU9rrBDOv@coredump.intra.peff.net>
[-- Attachment #1: Type: text/plain, Size: 1346 bytes --]
Hi,
On Tue, 19 Oct 2021, Jeff King wrote:
> On Tue, Oct 19, 2021 at 07:38:16PM +0200, BARDOT Jérôme wrote:
>
> > 2)
> >
> > I need a domain name / uri / ip base way to choose auth information.
> > i find some examples in past but not as smart as what i want. (Maybe i
> > miss something)
> >
> > 3)
> >
> > For auth client side can we use tools like Pass and or identity manager.
>
> I'm not entirely sure I understand your questions here, but I think
> you're looking for credential helpers? Try "git help credentials" for an
> overview.
>
> There are helpers which interact with common OS secure storage systems
> (like osxkeychain, libsecret, etc). But you can also write your own
> little scripts, and restrict them based on URLs.
>
> So for instance I use this config to pull a GitHub PAT out of the "pass"
> tool:
>
> [credential "https://github.com"]
> username = peff
> helper = "!f() { test $1 = get && echo password=`pass github/token`; }; f"
A quite complete, cross-platform credential helper (included in Git for
Windows and enabled by default, but it also works on macOS and on Linux)
is Git Credential Manager:
https://github.com/microsoft/Git-Credential-Manager-Core/
It comes with backends for some major Git hosters and is pretty
hassle-free, once configured.
Ciao,
Johannes
next prev parent reply other threads:[~2021-10-20 11:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 17:38 Questions, improvements BARDOT Jérôme
2021-10-19 21:31 ` Jeff King
2021-10-20 11:42 ` Johannes Schindelin [this message]
2021-10-20 12:40 ` BARDOT Jérôme
2021-10-21 0:39 ` brian m. carlson
2021-10-20 12:25 ` BARDOT Jérôme
2021-10-21 1:00 ` brian m. carlson
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=nycvar.QRO.7.76.6.2110201340370.56@tvgsbejvaqbjf.bet \
--to=johannes.schindelin@gmx.de \
--cc=bardot.jerome@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).