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 Date: Wed, 3 Jul 2002 17:48:38 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: sshd Message-ID: <20020703174838.D21857@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <01d601c2223c$d1a83880$7346f6cc AT baztech DOT com> <20020703103359 DOT O21857 AT cygbert DOT vinschen DOT de> <200207031006 DOT 47168 DOT g91 AT baz-tech DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200207031006.47168.g91@baz-tech.com> User-Agent: Mutt/1.3.22.1i On Wed, Jul 03, 2002 at 10:06:41AM -0500, Bryan Zimmer wrote: > -----BEGIN PGP SIGNED MESSAGE----- > /bin/bash (C:\Cygwin\bin\bash.exe) definitely exists and is executable. > However, it shows up only with ls -l /bin/bash.exe and not just > "/bin/bash", which surprised me. Me too. I can't reproduce that. What Cygwin version are you using? Are you sure not to have two Cygwin DLLs on your system? > My sshd is basically set up to accept hostbased or pubkey PubKey is ok but HostBased doesn't work on Cygwin since that requires a working s-uid bit concept. > authentication. It has two keys, ssh_host_rsa_key, and > ssh_host_dsa_key. It uses only protocol 2, never version 1. The public > user keys are kept in %h/.ssh/authorized_keys2. Most of the "easy" sshd ssh2 keys can be stored in .ssh/authorized_keys since 2.9 or so. You don't need an extra .ssh/authorized_keys2 file. > options are turned off. No RhostsRSAAuthentication, just RSA and DSA > authentication. I had these options "Allow Users baz; Deny Users > [A-Zac-z]*" which works in Linux, but I had to take it out for Cygwin. I wonder how that worked on Linux. According to `man sshd_config' only ? and * are allowed as wildcards. Other that that, the concept of AllowUsers, DenyUsers, AllowGroups and DenyGroups works on Cygwin the same way as on any other system. > I also had to make sure the "Strict Modes" option was "no". This is only needed under ntsec if you didn't set the modes and owners of the private files correctly. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT 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/