Re: SSH1 and SSH2 Keys Auth

"Keith Mastin" <[email protected]>
Newsgroups gmane.linux.redhat.release.enigma
Message-ID <[email protected]>
> Hello,
>
> I have a Script which uses Rsync with SSH Authentication to copy files
> from one server to another. It is a cronjob which executes every hour.
> The servers uses the DSA public Keys to Authenticate each other. So No
> passwd is asked while the cronjob is executed.
>
> Suddenly from couple of hours it started asking for the passwd from the
> cronjob and hence cannot rsync.

Can you go back through your logs to see if there were any incidents of
any note in the hour before the first fubar? Check messages, last and
secure.

> I am not looking for the solution from this list but could anyone
> suggest me where should i look what could be wrong. I checked from the
> prompt to connect to the same server but even then it asks for passwd.

This is a good question from you Tina. Perfectr for this list. If you
don't mind riding it out with us, we just might get you through it and
learn a thing or 2 ourselves in the meantime.

What concerns me here is that it was working and then suddenly went south.
You didn't do any changes to the systems at all, including running up2date
or adding/deleting users?

> I did a search in Google but it tell me how to setup the Auth.

Thank you. Troubleshooting is much easier if you've done some homework.
You're problem isn't in rsync, it's in sshd and the auth keys, which
you've identified. What happens if you set the keys and auth to RSA? If
this works, we've narrowed it down to the ssh daemon.

I had a similar issue once, where I set  a new set of keys and just cut
and pasted them into the server. The problem was that the newline breaks
on the console were also pasted, breaking the keys. The fix was to delete
the newline breaks, and !whammo! I was back in business.

HTH
-- 
Keith Mastin
BeechTree Information Technology Services Inc.
Toronto, Canada
(416)696 6070
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.