Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: Duncan Murdoch To: cygwin AT cygwin DOT com Subject: Re: ssh-agent: Cygwin version problems Date: Thu, 30 Sep 2004 05:20:47 -0400 Message-ID: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes I've discovered that some of the information in my post below is wrong: On Sun, 26 Sep 2004 10:54:29 -0400, Duncan Murdoch wrote: >I've been using OpenSSH with Cygwin for a while now, very >successfully. Thanks to all who put this together. > >I'd like to set up my machine for remote logins now, which makes me >much more security conscious: using an old version of OpenSSH is not >really an option. > >However, I can't find a way to get the latest OpenSSH to work without >messing up ssh-agent in the sense that it becomes strongly attached to >the bash window in which it was started. With the versions I've got >now, I can start ssh-agent, and an ssh tunnel, and then close the >window, and those processes keep running. This is very nice! > >As soon as I upgrade Cygwin, or the base files, this stops working. >The bash window refuses to close; if I tell Windows to shut it down, >it kills ssh-agent and ssh as well. This is wrong. ssh-agent is fine, it was ssh running some tunnels that was creating the zombie windows. I had a command line ssh -N -f -L [tunnel 1] -L [tunnel 2] [user AT host] >/dev/null 2>/dev/null