DKIM-Filter: OpenDKIM Filter v2.11.0 delorie.com 4A5BL1Ta1706921
Authentication-Results: delorie.com;
	dkim=pass (1024-bit key, unprotected) header.d=cygwin.com header.i=@cygwin.com header.a=rsa-sha256 header.s=default header.b=cx4x0iJB
X-Recipient: archive-cygwin AT delorie DOT com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org AE3D5385735B
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1730805659;
	bh=uSalaCOfxOI2UcLETbjtoUpzkj1weEIV50QPWL1z+rE=;
	h=To:Subject:Date:References:List-Id:List-Unsubscribe:List-Archive:
	 List-Post:List-Help:List-Subscribe:From:Reply-To:From;
	b=cx4x0iJB3CEMnWlfppp8qQNV/6F+Prp9hh7E7xWm9E+3+SIFV0i9mDSiOdmvB7FaW
	 4YpNc+GFPE0gZ8VvHcM744RwKnXR2SO068NiG+niV6TZ9mrGo/0bAbjTzu5LWp1mU5
	 TPez9+ffte17uv/AM3E+wDxI5tLN2x6+49u8Dbag=
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org EC46E3857439
ARC-Filter: OpenARC Filter v1.0.0 sourceware.org EC46E3857439
ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1730805602; cv=none;
 b=JWXeLfFa8lulCo/8ROt40Yt3uBDBP7iBw4h5edtQ1jw0xnPahnDosdxaFYx/ut0lDrlbvHDMzESzlh/QyGJAI2Q3tg9tjR96L7eoOuHvYceMDtKOlyNR1c+34w7FCkP8LZ9oG66HtROj4Trcd470z1gixXmno26jgyVUGEChn5k=
ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key;
 t=1730805602; c=relaxed/simple;
 bh=Zx0yCp1m7avK29MOrcRKM6uVq2p+SycuvFdPS3Spqrc=;
 h=To:From:Subject:Date:Message-ID:Mime-Version;
 b=B8Oa5ndYNClKNFVG0ReoCzHQPjAMF7S1a27zGMjO7Q8MjOqf7KuZnkS8HgwA3VcDOPyLdrMQIuLu46LhZwx96nwRQ8+eTFal2MzVVWTU3szjok6Pz1wjZhbj3vzxFx19jN8zu5iL6sADoQuLeXi4F36eLwNR4VU9RK90qkldQiE=
ARC-Authentication-Results: i=1; server2.sourceware.org
X-Injected-Via-Gmane: http://gmane.org/
To: cygwin AT cygwin DOT com
Subject: Re: cygport upload seems to ignore SSH_KEY
Date: Tue, 05 Nov 2024 06:19:43 -0500
Message-ID: <nlvjij9vha7u1j71seri65tfg21o7ua3im@4ax.com>
References: <8d85bde3-8ea8-4635-8547-9846315243cf AT kircheis DOT it>
 <7704ca4f-00ba-41b8-897c-7558d846ec18 AT SystematicSW DOT ab DOT ca>
Mime-Version: 1.0
X-Newsreader: Forte Agent 4.2/32.1118
X-Archive: encrypt
X-BeenThere: cygwin AT cygwin DOT com
X-Mailman-Version: 2.1.30
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
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: Andrew Schulman via Cygwin <cygwin AT cygwin DOT com>
Reply-To: Andrew Schulman <schulman DOT andrew AT epa DOT gov>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: "Cygwin" <cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com>

> On 2024-11-04 12:20, Federico Kircheis via Cygwin wrote:
> > up until recently I've uploaded packages the following way
> > export SSH_KEY=/path/to/id_rsa;
> > cygport /path/to/file.cygport upload
> > but today I got the following error
> > cd: Fatal error: max-retries exceeded
> > I've fixed it by copying my key in the .ssh folder
> > cp $SSH_KEY ~/.ssh/id_rsa
> > cygport /path/to/file.cygport upload
> > So it is not blocking me, but I wanted to know if this was a known bug, or if I 
> > am the only one experiencing it.
> 
> See
> 	https://cygwin.github.io/cygport/cygport_conf.html#SSH_KEY
> or
> 	/usr/share/doc/cygport/html/manual/cygport_conf.html#SSH_KEY
> 
> SSH_KEY
> 
> DESCRIPTION
> 
> Path to the SSH private key corresponding to the public key registered for 
> uploading on sourceware.
> You'll need to set this if your private key isn't already loaded into a running 
> ssh-agent(1), and it doesn't have one of the expected file names such as 
> ~/.ssh/id_rsa.
> Also, setting this allows cygport to determine if a passphrase is needed to 
> decrypt the key, and only prompt you for a passphrase if it's needed.
> Otherwise, you'll be prompted for a passphrase every time you upload.
> 
> Instead of `ssh-agent` and `ssh-add`, you can use `keychain` in your login 
> profile, which allows cross-session sharing, across X and terminal sessions, and 
> logouts, for example:
> 	$ eval `/usr/bin/keychain --noask --eval ~/.ssh/id_rsa`
> then
> 	$ keychain ~/.ssh/id_rsa

I haven't used cygport up in a long time - I use git push now, and let scallywag
build the packages - but this does seem like new wrong behavior. Surely he
shouldn't have to use keychain to get cygport to work? According to the docs, as
you cited, his method should work. Andrew


-- 
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