Shell Programming and Scripting

Hi Friends,

I was successfully able to login passwordlessly to server 1.1.1.2 from server 1.1.1.1 by following the below steps. I had already generated the keys using (ssh-keygen -t rsa) once and i am assuming i do not have to do that again.

Code:

 
ssh id@1.1.1.2 mkdir -p .ssh
cat .ssh/id_rsa.pub | ssh id@1.1.1.2 'cat >> .ssh/authorized_keys'
ssh id@1.1.1.2 "chmod 700 .ssh; chmod 640 .ssh/authorized_keys"

After doign the above, i am able to login successfully passwordlessly for some time. But after some hours, it again asks me for password. How to make this change permanent?

Why is it refusing it? ssh -v -v ...

I dint get you. The passwordless login thing is being reset somehow after initial setup . This is causing problems for me as i am unable to add a script to cron as the script has to login to the 2nd server to fetch data.
Can someone help

BTW, I copied the steps from here to login passwordlessly from 1 server to another

SSH Passwordless Login Using SSH Keygen in 5 Easy Steps

Update : OK, i got clue as to why this may be happening. I think the authorized_keys file is somehow getting deleted from server 2. When i again uploaded public keys to this file in server 2, it is showing new timestamp for today and it did not prompt for any overwrite or anything. So this authorized_keys file must be getting deleted. What could be the reason?

By ssh -v -v ... Corona688 wants you to increase the verbosity of the command output. It's easier for debugging.

Ok thanks for the explanation. As i understand, the function of the below codes is as explained

Code:

cat .ssh/id_rsa.pub | ssh id@1.1.1.2 'cat >> .ssh/authorized_keys' -- Upload public keys to Server 2 in a file authorized_keys
ssh id@1.1.1.2 "chmod 700 .ssh; chmod 640 .ssh/authorized_keys" --Give appropriate permission to authorized_keys

As i am suspecting that the authorized_keys is getting deleted from server 2 after 24 hrs(hence it is again asking for password while doing ssh from server 1). Shall i first check for the deletion of that file first and then run these commands(ssh -v -v) if the file has been deleted?

In the time it took you to read this thread and write that post you could have done both...

If the authorized_keys file is getting deleted:-If this is the case and you do want to keep re-creating it, then you may have to resort to a cron job on the server. Copy your authorized_keys file elsewhere, possibly outside ~/.ssh and as a different name, then copy it over each night.

I'm not suggesting that you breach your company rules though. You will need to adhere to company policy. If there is a rule, then there will be a reason. If you have a problem with it, it's best to discuss it rather than to circumvent it.



Robin


Robin