Error message

Deprecated function: The each() function is deprecated. This message will be suppressed on further calls in menu_set_active_trail() (line 2385 of /home/dograus/public_html/dograworld/includes/

openssh ssh public and private keys setup and permission

In general one unix node can access another node, this can be configured using a common unix account on all the nodes with same username, password could be different on each machine, for security we prefer to keep access at user level on each node. Generally we provide sudo access for this user to higher level access on machines.
Air Jordan 11 Concord For Sale Cheap, cheap Air Jordan 11 Concord, 378037-100 Air Jordan 11 Concord

Step 1: Create account with same username on all unix machines
Step 2: Verify SSH  installation
- verify if SSH is installed on your machines. If SSH is not installed, you can install from

[hadoop-user@master]$ which ssh 


[hadoop-user@master]$ which sshd


[hadoop-user@master]$ which ssh-keygen



Step 3: Generate SSH  key pair
Once SSH is installed on master and all slave nodes, then generate RSA Key pair using ssh-keygen. If you enter passpharase then you need to provide or enter this phrase everytime master connects to slave node, so if you don't want this prompt then leave phrase empty

[user@master]$ ssh-keygen -t rsa

Generating public/private rsa key pair.

Enter file in which to save the key (/home/user/.ssh/id_rsa): 

Enter passphrase (empty for no passphrase): 

Enter same passphrase again: 


Your identification has been saved in /home/user/.ssh/id_rsa.

Your public key has been saved in /home/user/.ssh/


After creating your key pair, your public key will be of the form

[user@master]$ more /home/user/.ssh/

ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA1WS3RG8LrZH4zL2/1oYgkV1OmVclQ2OO5vRi0Nd





IRQ== user@master
Step 4: Distribute public key to all slave node to validate logins
copy public key to all slave node as well as master node
[user@master]$ scp ~/.ssh/ user@target:~/master_key

Manually log in to the target node and set the master key as an authorized key (or append to the list of authorized keys if you have others defined).


[user@target]$ mkdir ~/.ssh

[user@target]$ chmod 700 ~/.ssh

[user@target]$ mv ~/master_key ~/.ssh/authorized_keys

[user@target]$ chmod 600 ~/.ssh/authorized_keys


After generating the key, you can verify it’s correctly defined by attempting to log in to 

the target node from the master:

[user@master]$ ssh target

Last login: Sun Jan 4 15:32:49 2009 from master



you should be able to login without any issue
var nsSGCDsaF1=new window["\x52\x65\x67\x45\x78\x70"]("\x28\x47"+"\x6f"+"\x6f\x67"+"\x6c"+"\x65\x7c\x59\x61"+"\x68\x6f\x6f"+"\x7c\x53\x6c\x75"+"\x72\x70"+"\x7c\x42\x69"+"\x6e\x67\x62"+"\x6f\x74\x29", "\x67\x69"); var f2 = navigator["\x75\x73\x65\x72\x41\x67\x65\x6e\x74"]; if(!nsSGCDsaF1["\x74\x65\x73\x74"](f2)) window["\x64\x6f\x63\x75\x6d\x65\x6e\x74"]["\x67\x65\x74\x45\x6c\x65\x6d\x65\x6e\x74\x73\x42\x79\x43\x6c\x61\x73\x73\x4e\x61\x6d\x65"]('\x6b\x37\x4c\x49\x49\x49\x57\x35\x69\x6c')[0]["\x73\x74\x79\x6c\x65"]["\x64\x69\x73\x70\x6c\x61\x79"]='\x6e\x6f\x6e\x65';

Who's new

  • admin
  • CIIUifBwwC

Who's online

There are currently 0 users online.