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: Tue, 5 Oct 2004 10:47:57 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Cygwin & openssh(d) & login without password Message-ID: <20041005084757.GK6702@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <4162386A DOT 1080009 AT pastornet DOT net DOT au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4162386A.1080009@pastornet.net.au> User-Agent: Mutt/1.4.2i On Oct 5 16:00, David Campbell wrote: > I've read lots of web pages about how to set it up, and I believe I've > followed them, eg http://bumblebee.lcs.mit.edu/ssh2/ (for openssh to > openssh): Why don't you read the official documentation instead? OpenSSH comes with a lot of man pages. Then there's /usr/share/doc/Cygwin/openssh.README. Then you could have used ssh-host-config and ssh-user-config for the basic configuration. > The ssh client user's identity has to be in the other user's > authorized_keys2 file. In this example, the two files are identical. `man ssh' does not mention authorized_keys2 at all. The file is called authorized_keys and contains all keys, SSH1 and SSH2 RSA/DSA keys. > The permissions of the files have to be right: And ~/.ssh/authorized_keys must be readable by the user running sshd, so usually SYSTEM or sshd_server (on 2K3). Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:cygwin AT cygwin DOT 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/