X-Recipient: archive-cygwin AT delorie DOT com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org CD4C43857C6F
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1636083646;
	bh=D5UbP2yudTG7wZIMowMWPml1Hk7omXRTjBkAw16XKXM=;
	h=Date:To:Subject:In-Reply-To:References:List-Id:List-Unsubscribe:
	 List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:
	 From;
	b=TUng5PUf4qW0SvKiEIDxCt8HsqLFAPe5mF9BoerwyTY/kvCEYfMLtrwMbt3ZxPPGx
	 EQ/nB/5d0PW4/vuGjkZc7CMLBYkNJgHVL3RtB9zjBnUL2ePQ/zjpRUusTYYdPLGnA3
	 3bNDcGNEfw50gCPRyBTjdB7xXtPm1bB/TfCpA6go=
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 43B643858406
DKIM-Filter: OpenDKIM Filter v2.10.3 conssluserg-02.nifty.com 1A53devA022105
X-Nifty-SrcIP: [110.4.221.123]
Date: Fri, 5 Nov 2021 12:39:50 +0900
To: cygwin AT cygwin DOT com
Subject: Re: 3.3.0: Possible regression in cygwin DLL (Win10); fixed in
 snapshot
Message-Id: <20211105123950.b118a7f2ba38379764df4c12@nifty.ne.jp>
In-Reply-To: <CAEv6GOB8PXHgHoz7hdJy6Bia2GWEmUDnTd252gTGinz2vuv=hA@mail.gmail.com>
References: <CAEv6GOB8PXHgHoz7hdJy6Bia2GWEmUDnTd252gTGinz2vuv=hA AT mail DOT gmail DOT com>
X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32)
Mime-Version: 1.0
X-Spam-Status: No, score=-5.3 required=5.0 tests=BAYES_00, DKIM_SIGNED,
 DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, NICE_REPLY_A, 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
X-BeenThere: cygwin AT cygwin DOT com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe: <https://cygwin.com/mailman/options/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From: Takashi Yano via Cygwin <cygwin AT cygwin DOT com>
Reply-To: Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>

On Thu, 4 Nov 2021 10:02:55 -0500
Brian wrote:
> GCM (Git Credential Manager) - Core fails to properly authenticate with
> previously stored credentials under the latest 3.3.0 release version of the
> Cygwin DLL (the bug itself and steps to recreate was originally submitted
> to the GCM-Core team here:
> https://github.com/microsoft/Git-Credential-Manager-Core/issues/509).  By
> replacing the Cygwin DLL with the 0913 snapshot, the problem no longer
> occurs. One of the GCM-Core devs suggested it might be a regression issue
> in the DLL.  Unfortunately, I don't have the C chops to explore this
> further.

Could you please provide the detailed steps to reproduce your problem?

-- 
Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp>

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple