From: Hans-Werner Hilse <hilse@web.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] [perhaps OT] ssh from Gentoo into a RedHat server
Date: Thu, 31 May 2007 14:38:53 +0200 [thread overview]
Message-ID: <20070531143853.8b66e0e0.hilse@web.de> (raw)
In-Reply-To: <200705311142.58519.michaelkintzios@gmail.com>
Hi,
On Thu, 31 May 2007 11:42:48 +0100 Mick <michaelkintzios@gmail.com>
wrote:
> > > Second, my id_dsa is my private key not my public key. My public
> > > key is id_dsa.pub
> >
> > but you will need your private key to be authenticated. that's why
> > it is *private*.
>
> That's right, so why does it:
> ======================================
> debug1: Trying private key: /home/michael/.ssh/id_rsa <--this doesn't exist
> debug1: Offering public key: /home/michael/.ssh/id_dsa <--this is my private key
> ======================================
What is wrong with that? It just says it is trying to access id_rsa,
not that there is one. So it fails, of course. So not existing key
isn't a matter here. It's _debugging_ output, so not necessarily
important information.
Using the private key is absolutely normal. A test message is encrypted
using it and is then being sent to the server, hence the term "offering".
I don't see what you are wondering about here.
> > > PS. Not sure if this is relevant but although my user name on the
> > > server is mick, for reasons better known to him the sysadmin has
> > > created my home directory as /home/mic - could it be that sshd is
> > > looking for /home/mick?
> >
> > that messages isn't from the server, is from client running
> > locally. but it doesnt matter for what you want.
>
> It matters if the server is trying to find id_dsa.pub in a
> non-existing directory.
But it _is_ a client message. It doesn't tell you where the server is
searching. So yes, the server might be off track and searching in the
wrong place. You could tell by monitoring the server's logs.
sshd will always search in the home directory as specified
in /etc/passwd (in the normal case) or more sophisticated solutions
like LDAP or NSS. So make sure it really *is* configured as the home
directory.
If the target server is ancient, it might also be searching in
".ssh/authorized_keys2". Maybe DSA auth is disabled. Why don't you
check server side logs (or let your sysadmin do that)?
-hwh
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2007-05-31 12:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-30 19:57 [gentoo-user] [perhaps OT] ssh from Gentoo into a RedHat server Mick
2007-05-30 20:12 ` Fabio
2007-05-30 21:43 ` Mick
2007-05-30 20:42 ` Mauro Faccenda
2007-05-31 10:42 ` Mick
2007-05-31 12:14 ` Mauro Faccenda
2007-05-31 13:08 ` Randy Barlow
2007-05-31 13:22 ` Hans-Werner Hilse
2007-05-31 14:23 ` Mick
2007-05-31 12:38 ` Hans-Werner Hilse [this message]
2007-05-31 13:26 ` Mauro Faccenda
[not found] ` <200705311928.27355.michaelkintzios@gmail.com>
2007-05-31 18:55 ` Randy Barlow
2007-05-31 19:05 ` Hans-Werner Hilse
2007-06-01 10:03 ` Mick
-- strict thread matches above, loose matches on Subject: below --
2007-05-31 15:02 Mick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070531143853.8b66e0e0.hilse@web.de \
--to=hilse@web.de \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox