[GE users] SSH and host keys

reuti reuti at staff.uni-marburg.de
Mon Feb 9 19:13:53 GMT 2009

Am 09.02.2009 um 19:52 schrieb opoplawski:

> Anyone know how to avoid the following:
> $ qrsh -l idllic=1
> The authenticity of host '[apollo.cora.nwra.com]:42115
> ([]:42115)' can't be established.
> RSA key fingerprint is be:14:c6:b3:7e: 
> 23:48:57:71:c2:02:75:74:7e:f4:ec.
> Are you sure you want to continue connecting (yes/no)?

You can set in the global or user ssh config like ~/.ssh/config

Host node*
     StrictHostKeyChecking no

and it will be added automatically. But there will be an entry for  
each selected port, hence it will get bigger and bigger. Are all  
nodes the same? Then you could use wildcards in the file ~/.ssh/ 
known_hosts like:

node*,192.168.* ssh-rsa AAAAB3NzaC1yc...

-- Reuti

> every time qrsh is run and the massive population of host keys it  
> causes?
> -- 
> Orion Poplawski
> Technical Manager                     303-415-9701 x222
> NWRA/CoRA Division                    FAX: 303-415-9702
> 3380 Mitchell Lane                  orion at cora.nwra.com
> Boulder, CO 80301              http://www.cora.nwra.com
> ------------------------------------------------------
> http://gridengine.sunsource.net/ds/viewMessage.do? 
> dsForumId=38&dsMessageId=102979
> To unsubscribe from this discussion, e-mail: [users- 
> unsubscribe at gridengine.sunsource.net].


To unsubscribe from this discussion, e-mail: [users-unsubscribe at gridengine.sunsource.net].

More information about the gridengine-users mailing list