All of lore.kernel.org
 help / color / mirror / Atom feed
From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Erik Cervin Edin <erik@cervined.in>
Cc: rsbecker@nexbridge.com,
	zhiyiren2009-subscription 
	<zhiyiren2009-subscription@protonmail.com>,
	zhiyiren2009@protonmail.com, snakamoto1975@protonmail.com,
	git@vger.kernel.org
Subject: Re: Quick login of git
Date: Tue, 28 Dec 2021 18:49:29 +0000	[thread overview]
Message-ID: <YctcOTeJUrBraa9M@camp.crustytoothpaste.net> (raw)
In-Reply-To: <CA+JQ7M94QXWbFnJfzewqecvETmJC9fVkFAb-+RHFuswj=FdnpA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1442 bytes --]

On 2021-12-28 at 17:15:26, Erik Cervin Edin wrote:
> > On December 27, 2021 11:07 AM zhiyiren2009-subscription wrote:
> > Why not add a quick login method like VSCode and CLion in git? Login
> > to
> > GitHub/ GitLab with one click, without privete key.
> 
> I believe you're referring to this?
> https://code.visualstudio.com/docs/editor/github#_authenticating-with-an-existing-repository
> 
> This is using PATs,
> so the same authentication can be used in CLI.
> 
> I recall seeing a github login window when I was playing around with https
> authentication in Git for Windows.
> Not sure what happens if you login through that as I quit that window.
> I believe the default credential helper already saves username/password
> for https remotes.

Git for Windows ships with the default credential helper as Git
Credential Manager Core, which will try to log in to some of the most
popular services with a native token.

However, this is not a part of core Git.  Folks who would like to use
this credential manager are welcome to do so, in which case it will work
for some services, but there's no way to automatically do this in the
general case, because it isn't guaranteed that a Git server provides an
automatic way to get a token.  For example, my personal Git server uses
only Kerberos authentication and doesn't issue tokens of any sort.
-- 
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

      reply	other threads:[~2021-12-28 18:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-27 16:06 Quick login of git zhiyiren2009-subscription
2021-12-27 16:14 ` rsbecker
2021-12-27 16:24   ` zhiyiren2009-subscription
2021-12-27 16:26     ` rsbecker
2021-12-27 19:15       ` zhiyiren2009-subscription
2021-12-27 19:50         ` rsbecker
2021-12-28  7:07           ` zhiyiren2009-subscription
2021-12-28 10:14           ` zhiyiren2009-subscription
2021-12-28 17:15           ` Erik Cervin Edin
2021-12-28 18:49             ` brian m. carlson [this message]

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=YctcOTeJUrBraa9M@camp.crustytoothpaste.net \
    --to=sandals@crustytoothpaste.net \
    --cc=erik@cervined.in \
    --cc=git@vger.kernel.org \
    --cc=rsbecker@nexbridge.com \
    --cc=snakamoto1975@protonmail.com \
    --cc=zhiyiren2009-subscription@protonmail.com \
    --cc=zhiyiren2009@protonmail.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.