![]() |
Hello and Welcome from United States to the UNIX and Linux Forums! Thank You for Visiting and Joining Our Global Community.
|
|
google unix.com
|
|||||||
| Forums | Register | Forum Rules | Links | Albums | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| SUN Solaris The Solaris Operating System, usually known simply as Solaris, is a free Unix-based operating system introduced by Sun Microsystems . |
More UNIX and Linux Forum Topics You Might Find Helpful
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Mount point options | Sunguy222 | UNIX for Advanced & Expert Users | 1 | 04-24-2008 06:23 PM |
| concept of mount point | Vikas Sood | UNIX for Dummies Questions & Answers | 3 | 06-08-2006 06:31 PM |
| mount point | colesy | UNIX for Dummies Questions & Answers | 1 | 01-06-2004 07:03 AM |
| Recover mount point | here2learn | UNIX for Dummies Questions & Answers | 1 | 11-11-2003 02:33 PM |
| sdX to mount point mapping | marist89 | UNIX for Dummies Questions & Answers | 2 | 10-24-2001 07:06 PM |
![]() |
|
|
LinkBack | Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
|
|
||||
|
ssh with shared mount point
I have 3 nodes and I want to set up ssh between them. Normnally I am fine with that but I am a bit stumped because for the Oracle user we have a shared mountpoint (/home/oracle) across all 3 nodes
I create my rsa and dsa files in ~/.shh as node1_id_rsa / node1_id_dsa (for each of the 3 modes) and then I cat each of the .pub files (both rsa and dsa) into the authorised_keys file. ssh still requires a password. The concept of the shared home area is confusing me a bit Can anybody else please |
|
||||
|
Shouldn't you be appending the certificate to $HOME/.ssh/authorized_keys?
Is the home directory shared between all 3 nodes, hence there is only one .ssh directory that is also shared? If so then this user can only have one default certificate identifying the user. |
|
||||
|
Porter, thanks for the response
I am appending the files to $HOME/.ssh/authorized_keys. There is only one .ssh directory. However if I run the ssh-keygen routine on node1 it creates .pub files with node1 in the line. Therefore if I try and connect from/to node 2 then it requires a password. Bear with me, I know I am not explaining myself very well |
|
||||
|
I have solved my problem
I needed to ssh-keygen -t rsa and ssh-keygen -t dsa to separate files for each node Then cat each node_id_rsa file into a clean file id_rsa and repeat for the node_id_dsa files into id_dsa. Then copy the relevant node_id_rsa.pub files and node_id_dsa.pub files into authorised_keys. Finally chmod 600 on the id_rsa and id_dsa files |
|
||||
|
I have a number of machines where I put exactly the same "identity" and "identity.pub" in my $HOME/.ssh directories because I am the same user.
This allows me to ssh and scp directly to any machine without having to use a password. And you would only need one entry in the authorized_keys, eg the same as identity.pub. known_hosts would accumulate the different machines you talk to of course. I use this to distribute my keys.... Code:
#!/bin/sh -x
ME=`whoami`
for d in $@
do
ssh <identity.pub $ME@$d cat \>\>.ssh/authorized_keys
if test "$?" = "0"
then
if ssh </dev/null $ME@$d chmod 600 .ssh/authorized_keys
then
ssh <identity $ME@$d dd of=.ssh/identity
ssh <identity.pub $ME@$d dd of=.ssh/identity.pub
ssh </dev/null $ME@$d chmod 600 .ssh/identity .ssh/identity.pub
ssh $ME@$d ls -l .ssh
fi
fi
done
|
![]() |
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|