[GE users] ssh_exchange_identification

Reuti reuti at staff.uni-marburg.de
Wed Jul 11 11:02:25 BST 2007


    [ The following text is in the "ISO-8859-1" character set. ]
    [ Your display is set for the "ISO-8859-10" character set.  ]
    [ Some special characters may be displayed incorrectly. ]

Am 11.07.2007 um 11:02 schrieb sadfub at gmx.net:

> Lönroth Erik schrieb:
>> This has to be your key being "bogus". Try regenerate the key  
>> correctly, I've seen this SSH error before:
>> ... and it was solved by fixing the keys which in this case are bad.
>
> Ok, I've done, as user, the following:
>
> -sh-3.00$ ssh-keygen -b 2048 -t rsa
> Generating public/private rsa key pair.
> Enter file in which to save the key (/home/me/.ssh/id_rsa):
> Enter passphrase (empty for no passphrase):
> Enter same passphrase again:
> Your identification has been saved in /home/me/.ssh/id_rsa.
> Your public key has been saved in /home/me/.ssh/id_rsa.pub.
> The key fingerprint is:
> 43:61:1e:8c:a5:12:e8:8f:96:b5:09:44:5b:3e:ea:40 me at frontend
>
> -sh-3.00$ ssh-keygen -i -f id_rsa
> buffer_get_string: bad string length 813827233
>
> -sh-3.00$ ssh-keygen -i -f id_rsa.pub
> uudecode failed.

Your own keys you don't have to convert. It's meant to convert keys  
from a commercial ssh-keygen (which includes these "---BEGIN..."  
statements into the openSSH format, hence you can put a public key  
from a Windows machine with e.g. Tectia from ssh.com into the  
authorized_keys file in an openSSH server this way).

-- Reuti


> this last two commands finishing me >-(, I don't know why the ****  
> this
> ssh couldn't reread it's own keys? Hmm. Anyhow the login thorugh `ssh
> nodeXY` works without any error nor password promt as expected.  
> Despite
> that ssh-keygen issue, if I do a `qrsh hostname` with root privileges
> every works as expected. But as user I still get:
>
> -sh-3.00$ qrsh -verbose hostname
> Your job 158706 ("hostname") has been submitted
> waiting for interactive job to be scheduled ...
> Your interactive job 158706 has been successfully scheduled.
> Establishing /usr/bin/ssh session to host node03 ...
> Warning: No xauth data; using fake authentication data for X11  
> forwarding.
> qrsh_starter: executing child process (null) failed: No such file or
> directory
> /usr/bin/ssh exited with exit code 0
> reading exit code from shepherd ... 1
>
> thanks for your help.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
> For additional commands, e-mail: users-help at gridengine.sunsource.net

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
For additional commands, e-mail: users-help at gridengine.sunsource.net




More information about the gridengine-users mailing list