From owner-freebsd-hackers  Sun Aug 24 23:07:41 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id XAA21772
          for hackers-outgoing; Sun, 24 Aug 1997 23:07:41 -0700 (PDT)
Received: from verdi.nethelp.no (verdi.nethelp.no [195.1.171.130])
          by hub.freebsd.org (8.8.7/8.8.7) with SMTP id XAA21761
          for <hackers@hub.freebsd.org>; Sun, 24 Aug 1997 23:07:35 -0700 (PDT)
From: sthaug@nethelp.no
Received: (qmail 2741 invoked by uid 1001); 25 Aug 1997 06:07:27 +0000 (GMT)
To: ahd@FreeBSD.ORG
Cc: hackers@hub.freebsd.org
Subject: Re: debugging ssh "Access Denied"
In-Reply-To: Your message of "Sun, 24 Aug 1997 14:11:08 -0700 (PDT)"
References: <199708242111.OAA21649@hub.freebsd.org>
X-Mailer: Mew version 1.05+ on Emacs 19.28.2
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Date: Mon, 25 Aug 1997 08:07:27 +0200
Message-ID: <2739.872489247@verdi.nethelp.no>
Sender: owner-freebsd-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> When defining a new ssh connection (in my case, my own system into
> hub.freebsd.org), how does a mortal (I have root on my system, but
> of course not hub) debug problems which result in "Permission
> Denied" messages?

"ssh -v" is usually a good start. If you also have access to syslog
at the other end, and sshd is configured with "FascistLogging yes",
it's usually pretty simple to debug problems.

Steinar Haug, Nethelp consulting, sthaug@nethelp.no