Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Tue, 27 Aug 2002 11:07:15 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: ssh.exe strange behaviour Message-ID: <20020827110715.S5475@cygbert.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <000f01c24ccb$a5bd16a0$eb6610ac@lefeuvrewk2> <20020826102249.C5475@cygbert.vinschen.de> <004c01c24cdc$4c111820$eb6610ac@lefeuvrewk2> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <004c01c24cdc$4c111820$eb6610ac@lefeuvrewk2> User-Agent: Mutt/1.3.22.1i On Mon, Aug 26, 2002 at 10:40:57AM +0200, Corwin wrote: > Thanks Corinna, > > I agree it is very unlikely. > When I say by itself, I only mean that I did not tell it to connect to any > of these adresses. > Taking this into account, if I did not call ssh myself, then another app did > it... > The only thing I can say is that this happened when launching kde (using > XManager as X Server). > Would it be possible that kde did this ? *shrug* Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin@cygwin.com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/