From: Yaakov Selkowitz <yselkowi@redhat.com>
To: cygwin-apps@cygwin.com
Subject: Re: github password policy
Date: Mon, 16 Aug 2021 13:59:00 -0400 [thread overview]
Message-ID: <cf35154201c5cb2370bcc3cac913f9bc6003760c.camel@redhat.com> (raw)
In-Reply-To: <c98bed81-fc7d-cbfe-5e35-af4e0968f588@towo.net>
On Mon, 2021-08-16 at 19:51 +0200, Thomas Wolff wrote:
>
> Am 16.08.2021 um 16:46 schrieb Lee:
> > On 8/16/21, Thomas Wolff wrote:
> > > github have changed their authentication policy not to allow passwords
> > > anymore.
> > > So they are asking maintainers to acquire another kind of password (a
> > > "token"), which I did a while ago.
> > > But they refuse to support users with the transition, there is no
> > > "plug-and-play" howto available, except for those who are willing to
> > > dive into details of authentication stuff and spend a few study hours on
> > > that useless policy change.
> > > As I cannot update mintty anymore right now from the git command line,
> > > is any maintainer here impacted by the same issue and can help out with
> > > some advice how to get rid of this nuisance?
> > ssh keys work - start here:
> > https://docs.github.com/en/github/authenticating-to-github/connecting-to-github-with-ssh
> Thanks for the link. So I've now added my ssh key to github and
> successfully tested it.
> Now what? git push apparently still wants to use the old password and
> reports an error.
Make sure the (push)url for the remote to which you wish to push is in the
form git@github.com:NAMESPACE/PROJECT.git rather than an https:// form.
--
Yaakov Selkowitz
Senior Software Engineer - Platform Enablement
Red Hat, Inc.
next prev parent reply other threads:[~2021-08-16 17:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-16 12:13 Thomas Wolff
2021-08-16 13:44 ` ASSI
2021-08-16 23:59 ` Doug Henderson
2021-08-17 3:00 ` Brian Inglis
2021-08-18 17:12 ` Thomas Wolff
2021-08-16 14:44 ` Corinna Vinschen
2021-08-16 14:46 ` Lee
2021-08-16 17:51 ` Thomas Wolff
2021-08-16 17:59 ` Yaakov Selkowitz [this message]
2021-08-17 6:39 ` Thomas Wolff
2021-08-16 18:33 ` Jonathan Yong
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=cf35154201c5cb2370bcc3cac913f9bc6003760c.camel@redhat.com \
--to=yselkowi@redhat.com \
--cc=cygwin-apps@cygwin.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 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).