Re: Key fail, says OK instead

Path	csiph.com!x330-a1.tempe.blueboxinc.net!newsfeed.hal-mli.net!feeder3.hal-mli.net!nx01.iad01.newshosting.com!newshosting.com!69.16.185.16.MISMATCH!npeer02.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!post01.iad.highwinds-media.com!newsfe12.iad.POSTED!b20e9f34!not-for-mail
From	Richard E. Silverman <res@qoxp.net>
Newsgroups	comp.security.ssh
Subject	Re: Key fail, says OK instead
References	<iusl2k$2qk$1@speranza.aioe.org>
Message-ID	<m2oc16yarj.fsf@darwin.oankali.net> (permalink)
User-Agent	Gnus/5.13 (Gnus v5.13) Emacs/23.3 (darwin)
Cancel-Lock	sha1:DfV/Oo8lx4M9F0ceBrLQOvLZEuA=
MIME-Version	1.0
Content-Type	text/plain; charset=us-ascii
Lines	24
X-Complaints-To	abuse@thundernews.com
NNTP-Posting-Date	Thu, 07 Jul 2011 04:28:50 UTC
Organization	Thundernews
Date	Thu, 07 Jul 2011 00:28:48 -0400
Xref	x330-a1.tempe.blueboxinc.net comp.security.ssh:131

Show key headers only | View raw

Sensei <sensei.wa@apple.me.com> writes:

> Dear all,
>
> I have set up a SSH server with a private key login. It worked perfectly
> from my client, until yesterday, when a back-out hit my client. Now, it
> does not work...

The debug trace shows that the client is offering the key to the server;
beyond that, there's nothing more to learn here.  You need info from the
server:

1) Check permissions on the server: OpenSSH requires that ~, ~/.ssh, and
   ~/.ssh/authorized_keys be writable only by root or the target
   account.

2) Check syslog for messages from sshd.

3) If you can, run the server in debug mode (e.g. /usr/sbin/sshd
-dep221), connect to it (ssh -vp221), and see what the server says.

- Richard

Back to comp.security.ssh | Previous | Next — Previous in thread | Find similar

Thread

Key fail, says OK instead Sensei <sensei.wa@apple.me.com> - 2011-07-04 17:09 +0200
  Re: Key fail, says OK instead Richard E. Silverman <res@qoxp.net> - 2011-07-07 00:28 -0400

csiph-web