From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lj1-x22e.google.com (mail-lj1-x22e.google.com [IPv6:2a00:1450:4864:20::22e]) by sourceware.org (Postfix) with ESMTPS id 3BB943858D28 for ; Fri, 5 Nov 2021 13:42:15 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 3BB943858D28 Received: by mail-lj1-x22e.google.com with SMTP id v15so7959631ljc.0 for ; Fri, 05 Nov 2021 06:42:15 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=eSfP0e95s/ZpHkFuMiYd704FjsF3fZ5HItt00zks4NQ=; b=K7wJnOb7aAH2zriio9Pfi3ocUZGhyolnYH57JrGL1qk9RiepCxe9Ph8b22USnliYNV BJL0z4JlU+Zs3ddtV+CMYP0jKZT1mXX13sQYv6vxM79rXZotZX7URF3i2Fy+mEyKkAPc V9ZGZqXISg3oskbkBQaYo8ba7WHe7ZlncQE3imdLDogE8s/8We6Q75Saj/AwCIE3xAqQ qcjIlAT7hqRIO0gHKsuIsWZ8nZ2uX/PjEkPD41WLEn46M2GV8NNUVNDS+dwgTef30RWz stuCLuvaLuWRfpLiUNeBvQ5Xu3wIJH7FdFquA3Fml0ZtelxhQRtlypdNxTEmbasZCL7g jTPw== X-Gm-Message-State: AOAM531zC4mL5/phKSB3RbpcP3jjtzKP8Y/+C7SzuC0GmTUa08SxgZbo 7IHRggrh9j/WKgAq/SkKO3Qzx6alfd6GnRGhaf0= X-Google-Smtp-Source: ABdhPJxxTHCyoNFkepmo7KVeSJQyp/awWI5iF3T8yb4xSF7T9dA/00viZuTlW0F715RVl9drstJbg8wFCGF+py3A4RE= X-Received: by 2002:a05:651c:1181:: with SMTP id w1mr22637619ljo.424.1636119733967; Fri, 05 Nov 2021 06:42:13 -0700 (PDT) MIME-Version: 1.0 References: <20211105123950.b118a7f2ba38379764df4c12@nifty.ne.jp> <20211105170542.96ce6dd4ca32880ddfddd660@nifty.ne.jp> In-Reply-To: <20211105170542.96ce6dd4ca32880ddfddd660@nifty.ne.jp> From: Brian Date: Fri, 5 Nov 2021 08:42:03 -0500 Message-ID: Subject: Re: 3.3.0: Possible regression in cygwin DLL (Win10); fixed in snapshot To: Takashi Yano Cc: cygwin@cygwin.com X-Spam-Status: No, score=-0.6 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, HTML_MESSAGE, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, 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 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: cygwin@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Nov 2021 13:42:17 -0000 Starting point: Cygwin 3.3.0s(0.341/5/3), Windows Version 10.0.17763 Build 17763, no git managers/clients initially installed. 1. Install git version 2.33.0 via the Cygwin installer (only the CLI). 2. Download the GCM-Core 2.0.567 release zip file ( https://github.com/microsoft/Git-Credential-Manager-Core/releases/) and extract somewhere. 3. Copy all *.exe and *.dll files to your Cygwin /usr/libexec/git-core/ directory. 4. Set up the credential helper: 'git config --global credential.helper manager-core' 5. Clone a repo. 6. Attempt a 'git push' using the git repo's https URL. GCM will pop up a browser-based UI for initial authentication. After entering username and PAT credentials, and receiving the 'Everything is up-to-date' message, confirm that your git credentials appear in the Windows Credential Manager. 7. Attempt another 'git push'. EXPECTED BEHAVIOR: 'Everything is up-to-date' (there should be no CLI or UI authentication prompts). OBSERVED BEHAVIOR: The user is again presented with an authentication prompts from git. 8. Replace cygwin1.dll with the 0913 snapshot. 9. Attempt a 'git push'. If your credentials were cached in WCM per step 6, you should immediately see the 'Everything is up-to-date' reply. If your credentials weren't stored for some reason, you will be prompted for authentication. A subsequent 'git push' should then use your cached credentials. Please let me know if there are any other steps you think might be missing. --Brian