Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Secure-Shell
[Top] [All Lists]

Re: Why am I sending the publickey?

Subject: Re: Why am I sending the publickey?
Date: Mon, 20 Mar 2006 16:14:56 +0000
On Mon, 2006-03-20 at 10:12 -0500, Zembower, Kevin wrote:

debug1: Authentications that can continue:
publickey,password,keyboard-interactive
debug1: Next authentication method: publickey
debug1: Trying private key: /root/.ssh/identity
debug1: Offering public key: /root/.ssh/id_rsa
Connection closed by xx.xx.xx.xx
[root@xxx .ssh]#

I don't understand why it's trying the publickey method.

On the remote host, I've removed the lines in /root/.ssh/authorized keys
for the host I'm coming from, and restarted sshd,

Your client is offering a key because your server is indicating a
willingness to accept one (this is controlled by sshd_config, not
authorized_keys).

There's some brokenness here though; it's not clear why the connection
is closing immediately after the public key is offered. It should refuse
it, then move on to the other authorisation methods. A sudden closure
suggests that your server process is aborting (e.g. a segmentation
violation). How confident are you that your server build is reasonable?

- Raz

<Prev in Thread] Current Thread [Next in Thread>