From owner-freebsd-questions Fri Oct 26 8: 6: 2 2001 Delivered-To: freebsd-questions@freebsd.org Received: from mail.utexas.edu (wb3-a.mail.utexas.edu [128.83.126.138]) by hub.freebsd.org (Postfix) with SMTP id C4AC137B406 for ; Fri, 26 Oct 2001 08:05:56 -0700 (PDT) Received: (qmail 17019 invoked by uid 0); 26 Oct 2001 15:05:55 -0000 Received: from chepe.cc.utexas.edu (HELO oscar.mail.utexas.edu) (128.83.135.25) by umbs-smtp-3 with SMTP; 26 Oct 2001 15:05:55 -0000 Message-Id: <5.1.0.14.2.20011026095903.00ae6dd8@mail.utexas.edu> X-Sender: oscars@mail.utexas.edu X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Fri, 26 Oct 2001 10:04:31 -0500 To: "Mark Hughes" , questions@freebsd.org From: Oscar Ricardo Silva Subject: Re: DSA authentication using SSH In-Reply-To: <064f01c15e22$ecfd8060$0200a8c0@mark2> References: <5.1.0.14.2.20011026081150.00a6f5d0@mail.utexas.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 02:33 PM 10/26/2001 +0100, Mark Hughes, you wrote: >[oops, replied from the wrong account, let me try again] > > > Although I don't have a real solution, here are two things to try: > > > > 1. Check the permissions on the 'authorized_keys' file on the machine > > you're trying to connect to. Mae sure only the owner has permissions. > >Yup, i've checked this many times. What is the name of the file where you put the public keys on the target machine? How did you build the keys? I believe the default when running ssh-keygen is to build version 1 of rsa keys. Are you sure that when you copied the public key to the authorized_keys file on the target machine that it was one long line? It may look like more than one line and some editors may break it up into two, but the key should stay as one long line. > > 2. Before going much farther, update to OpenSSH 2.9.9p2. This way you > > make sure it's not something specific to the version you're running. > >I thought that may be the case, so I tried to upgrade to the latest version >of openSSH - using /usr/ports/security/openssh && make install as root. >This installed the latest version, as far as I can tell, but ssh -v still >reports the old (2.3.0) version number...any ideas? > >Is it just that there hasn't been any changes in the ssh program for a >while, or have I upgraded wrong? In this case, this version of OpenSSH is fairly recent so unlikely to be found in the ports. I upgraded by downloading the source and building from there. One note of caution, OpenSSH components that come with FreeBSD are installed in /usr/bin, /usr/sbin, and configuration in /etc/ssh. The default in building from source is to install these components in /usr/local/bin, /usr/local/sbin, /usr/local/etc. Make sure to read the output from "./configure --help" before building. Oscar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message