From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [216.205.24.124]) by sourceware.org (Postfix) with ESMTP id 231CC395201D for ; Mon, 16 Aug 2021 17:59:04 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 231CC395201D Received: from mail-qv1-f71.google.com (mail-qv1-f71.google.com [209.85.219.71]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-529-FLnrxSPJML6JQX1EcH2oOQ-1; Mon, 16 Aug 2021 13:59:02 -0400 X-MC-Unique: FLnrxSPJML6JQX1EcH2oOQ-1 Received: by mail-qv1-f71.google.com with SMTP id u6-20020ad448660000b02903500bf28866so13482952qvy.23 for ; Mon, 16 Aug 2021 10:59:02 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:date:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=cItyjktoYtVOTLSFxE0RJ0olPGVlon/1TbOQyq9dlAI=; b=LerIykRVBgl0Dtz2xFRo+EEPg4PAdIHaHv9wOhQGsk5GFDW3VlQ15e5Lm1GphTammr 6cSnQl4hcejpVpJWgrvdpjwaKYuSzKbHKrhmwTZ14958ZjQdPNa75J158XHWyyvjUFzK wBIGdMThRLw/v5jMzjOmR1Rc2wDtDfRE2uQSpwrVAF6cFgrUgB929lvLE16ZauimWthK fpZYZaqT6fEICd5AIRiMf4LWEzqc5N4AoOwEVycHG+jimtzknz2h7RFgf/r6+hHsbTaD 8j78v7Q5zgUYSB0NbqbhdDOJax30i3XWj6n5NC8vA3TwgNQwAycTJaU2gVq00vcQEPd/ fjBA== X-Gm-Message-State: AOAM5327v4BnrngD3BkfHXNBEhnPChZNXjsMQ8w3j2QgRMc/e0BClwIP KRq3KlJWhGJ5zfkQzIVQiO1fBOonGQPx2+yOoJEHJlzMg9iTXAWGquSHbL0f4Nnibo7PkJf2lDd nn8kVi1X6RImAV7EBXFG5ZY/+CatjriUdgJ0H3lpFBJVI3YHVpWnVdzmqcdyJ9EftEw1l X-Received: by 2002:ac8:574e:: with SMTP id 14mr138642qtx.300.1629136741789; Mon, 16 Aug 2021 10:59:01 -0700 (PDT) X-Google-Smtp-Source: ABdhPJy9/sfN5bx4Us3vmqo97k4/bANkbTyZLq7meW83vySTAWjdTL8eCoeBnH5qNI4n/JOGLoTVhg== X-Received: by 2002:ac8:574e:: with SMTP id 14mr138600qtx.300.1629136741348; Mon, 16 Aug 2021 10:59:01 -0700 (PDT) Received: from yselkowitz.remote.redhat.com (bras-base-toroon6128w-grc-28-184-145-131-42.dsl.bell.ca. [184.145.131.42]) by smtp.gmail.com with ESMTPSA id n14sm5249451qti.47.2021.08.16.10.59.00 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 16 Aug 2021 10:59:01 -0700 (PDT) Message-ID: Subject: Re: github password policy From: Yaakov Selkowitz To: cygwin-apps@cygwin.com Date: Mon, 16 Aug 2021 13:59:00 -0400 In-Reply-To: References: User-Agent: Evolution 3.40.3 (3.40.3-1.fc34) MIME-Version: 1.0 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-3.6 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H2, SPF_HELO_NONE, SPF_NONE, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: cygwin-apps@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Cygwin package maintainer discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Aug 2021 17:59:06 -0000 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.