Hi, could somebody help me, please...

on my slackware machine when i run out next 2 commands,

1.
root@intel333:~$ ssh-agent /bin/bash -everything looks ok

2.
root@intel333:~$ ssh-add -l
The agent has no identities. <<<<< problem is that ssh-add stop responding in that moment, even if a identity is added or if ssh-add command is executed before, it shows only error below:

root@intel333:~$ ssh-add
Could not open a connection to your authentication agent.


So ssh-agent must be executed at first and then ssh-add for adding key's, on my second fedora machine this proces works ok, so now i dont know where's the problem.

Is this what you want to do to make it not ask for passphrase?

I do it as follows for rsa. Same for dsa just make the change.

exec ssh-agent /bin/bash
ssh-add ~/.ssh/id_rsa
enter passphrase

Brian1

1 members found this post helpful.

I'm not sure because of this:

[vikes@amd64 ~]$ ssh intel333
vikes@intel333's password:
Last login: Sat May 6 02:48:18 2006 from amd64
Linux 2.4.31.
vikes@intel333:~$ ssh-agent /bin/bash
vikes@intel333:~$ man ssh-add <<<< after this command terminal stop responding, same in next case

vikes@intel333:~$ ssh-agent /bin/bash
vikes@intel333:~$ ssh-add --help <<<<< just blinking cursor on screen, and must login again.


Permissions of files are set to only owner can acces this file(identity, i'm using rsa1 for testing purposes) in ~/.ssh, and on seconfd machine this process works ok. My target is to authentificate from amd64(fedora) without password and passphrase on intel333(slack-server). I has read out book about SSH, but a still can solve this issue. Now i've got mixture in head, if you could provide me quick help i'll be thankful please.

I'm not sure because of this:

[vikes@amd64 ~]$ ssh intel333
vikes@intel333's password:
Last login: Sat May 6 02:48:18 2006 from amd64
Linux 2.4.31.
vikes@intel333:~$ ssh-agent /bin/bash
vikes@intel333:~$ man ssh-add <<<< after this command terminal stop responding, same in next case

vikes@intel333:~$ ssh-agent /bin/bash
vikes@intel333:~$ ssh-add --help <<<<< just blinking cursor on screen, and must login again.


Permissions of files are set to only owner can acces this file(identity, i'm using rsa1 for testing purposes) in ~/.ssh, and on seconfd machine this process works ok. My target is to authentificate from amd64(fedora) without password and passphrase on intel333(slack-server). I has read out book about SSH, but a still can solve this issue. Now i've got mixture in head, if you could provide me quick help i'll be thankful please.
__________________

The above post is confusing me. Looks like you have logged into remote ssh server and then trying to run the sss-agent command there. You run the command on the local box before making the connection.

Check out this link of ssh setup. Great site. http://www.suso.org/docs/shell/ssh.sdf

Question: You have setup passphrase and the remote site is not asking for the passphrase? Just the password?
If so follow this from the above web site link.
Now when ssh to the remote machine, it should ask you for your key passphrase instead of your password. If it doesn't, it could be that the permissions and mode of the authorized_keys file and .ssh directory on the remote server need to be set more restrictively. You can do that with these commands on the remote server:

chmod 700 ~/.ssh
chmod 600 ~/.ssh/authorized_keys


Brian1

Thank you very much, ssh connection now works fine, as i wish, but the problem what i've described previously before is still reoccuring.

amd64 machine:

[vikes@amd64 .ssh]$ ssh-add -l
The agent has no identities.
[vikes@amd64 .ssh]$

slack machine:

vikes@intel333:~$ ssh-add -L
The agent has no identities.
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<cursor blinks, and terminal after this not responding

Altrough, thanx again, you helps me, its good that this forum exist, i like this linux world...

Cheers.

Have followed the ssh-agent like it is described in the suso link?
If so then I have no idea. I am guessing something is missing. What I do not know.
How about installing the latest. Or going to apps site and see if there are any bugs.

Brian1