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, 17 Feb 2004 22:24:25 +0100 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: 2004-Feb-17 snapshot change ssh option parsing behavior Message-ID: <20040217212425.GB18953@cygbert.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <16434.32879.365152.633519@forbin.entomo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <16434.32879.365152.633519@forbin.entomo.com> User-Agent: Mutt/1.4.2i On Feb 17 12:58, David Rothenberger wrote: Content-Description: message body text > Prior to using the 2004-Feb-17 snapshot, the command > > % ssh somehost /bin/bash --login -c date > > worked correctly. Now, ssh gives "Unknown cipher type 'date'." We're using the latest plain BSD getopt() now. It's permuting the options by default. This was switched off by default in Cygwin so far. Typically you should quote the command you send to the remote host: ssh somehost '/bin/bash --login -c date' I did that already all the time so I never hit the above situation. Another way to accomplish what you want is to set the environment variable POSIXLY_CORRECT prior to calling ssh. 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 Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/