From owner-freebsd-security Wed Mar 6 8: 7:36 2002 Delivered-To: freebsd-security@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id 5697737B404 for ; Wed, 6 Mar 2002 08:07:32 -0800 (PST) Received: (from mwlucas@localhost) by blackhelicopters.org (8.11.6/8.11.6) id g26G7VE00759 for security@freebsd.org; Wed, 6 Mar 2002 11:07:31 -0500 (EST) (envelope-from mwlucas) Date: Wed, 6 Mar 2002 11:07:31 -0500 From: Michael Lucas To: security@freebsd.org Subject: ssh keys not working? Message-ID: <20020306110730.A720@blackhelicopters.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Folks, I just installed -current on my laptop so I can start to document the bugger, and have everything installed and running properly, except SSH key handling. When I try to SSH somewhere, the local key is obviously not being picked up. I show ssh-agent is running, and a check of my environment shows SSH_AGENT_PID and SSH_AUTH_SOCK. /etc/ssh/ssh_config explicitly lists "RSAAuthentication yes". Any other suggestions on what to check? (Of course, this means that my commit bit is now useless unless I boot into -stable... found myself with time to work today, and I just can't, dang it! And it's only worse because I know there's some stupid little thing I'm missing.) Thanks, Michael -- Michael Lucas mwlucas@FreeBSD.org, mwlucas@BlackHelicopters.org my FreeBSD column: http://www.oreillynet.com/pub/q/Big_Scary_Daemons http://www.blackhelicopters.org/~mwlucas/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message