From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29614 invoked by alias); 13 Feb 2015 04:10:26 -0000 Mailing-List: contact cygwin-apps-help@cygwin.com; run by ezmlm Precedence: bulk Sender: cygwin-apps-owner@cygwin.com List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps@cygwin.com Received: (qmail 29554 invoked by uid 89); 13 Feb 2015 04:10:21 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.6 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS autolearn=ham version=3.3.2 X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Fri, 13 Feb 2015 04:10:20 +0000 Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id t1D4AJGX029263 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for ; Thu, 12 Feb 2015 23:10:19 -0500 Received: from YAAKOV04.redhat.com ([10.10.116.21]) by int-mx11.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id t1D4AIQY006998 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NO) for ; Thu, 12 Feb 2015 23:10:19 -0500 Message-ID: <1423800617.12472.192.camel@cygwin.com> Subject: Re: [RFC] cygport upload From: Yaakov Selkowitz To: cygwin-apps@cygwin.com Date: Fri, 13 Feb 2015 04:10:00 -0000 In-Reply-To: References: <1423780937.12472.183.camel@cygwin.com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2015-02/txt/msg00165.txt.bz2 On Thu, 2015-02-12 at 20:23 -0500, Andrew Schulman wrote: > > I have created an upload branch in cygport git based on master with > > Andrew's upload work for further testing. > > FWIW, I've been using it to upload my packages since the last update on Jan. 17, > and before that too, with no problems. > > I always keep my ssh keys loaded in a running ssh-agent, so I've tested that > case pretty well. I think it would be most useful to test the other cases: > ssh-agent running but key not loaded; ssh-agent not running; private keys > encrypted/unencrypted. I am testing it both with an ssh-agent (gnome-keyring) and without, and my keys are encrypted. -- Yaakov