옥탑방람보

SRC-POINT -> DEST-POINT

1. Setting up SSH key authentication (mostly skip this step)
First, you need to make sure the DEST-POINT has the ability to user key autherntication enabled.

> vi /etc/ssh/sshd_config
RSAAuthentication yes
PubkeyAuthentication yes
AuthorizedKeysFile .ssh/authorized_keys
> /etc/init.d/sshd restart
 
2. Generation SSH public key in SRC-POINT
> ssh-keygen -t rsa
(*note: do not enter any passphrases on this, just hit enter when prompted)
 
3. Planting the public key to DEST-POINT
> vi ~/.ssh/authorized_keys
Add the public key of SRC-POINT
(*note:  user1> cat ~/.ssh/id_rsa.pub | ssh user1@DEST-POINT 'cat >> ~/.ssh/authorized_keys')
> chmod 755 ~/.ssh  (DEST-POINT)
> chmod 644 ~/.ssh/authorized_keys  (DEST-POINT)
(*note: check permissions all above directories of the "~/.ssh". If Group or Other permissions in them have "Write", sync between the two points are broken.)
 
 
* in Cluster (rocks)
In the default Rocks cluster configuration, /home is an automount directory. All nodes in the cluster system can mount the Home directory when an user accesses to each node.
Therefore, in cluster system, directories generated public key of SRC-POINT and DEST-POINT are same. "id_rsa.rsa" and "authorized_keys" files are located in same directory of an user home.
> ssh-keygen -t rsa
> cat ~/.ssh/id_rsa.pub >> ~/.ssh/authorized_keys

1. Make sure DNS is properly configured on your system. Slow SSH logins are often caused by a name resolution timeout. Does your primary name server have entries for the systems from which you are connecting? Are the reverse lookup entries in place?  (from rocks-discuss)

2. If the server can not use DNS, enroll your local IP into /etc/hosts.
> vi /etc/hosts
IP_ADRESS   YOURHOSTNAME

#User specific

#alias
alias vi='vim'
alias rm='rm -i'
alias ll='ls -lF --color'
alias ls='ls --color'
alias python='time python'
alias pyt='time python'
alias qstat='qstat -u "*"'
alias du='du -c'

#kimps path
export KIMPS=/home/user/kimps/
#kimps bin
export KIMPSUTILS=$KIMPS/bin/
if [ -d ${KIMPSUTILS} ]
then
   for i in ${KIMPSUTILS}/*; do
      if [ -d "$i" ]; then
         PATH=$PATH:$i/
      fi
   done
   unset i
fi
export PATH=$KIMPSUTILS:$PATH

#user bin
export USERBIN=/home/user/bin/
if [ -d ${USERBIN} ]
then
   for i in ${USERBIN}/*; do
      if [ -d "$i" ]; then
         PATH=$PATH:$i/
      fi
   done
   unset i
fi
export PATH=$USERBIN:$PATH

#exports
export PYTHONPATH=/home/user/install/Python-2.6.7/Lib/site-packages:$PYTHONPATH
export CATALINA_HOME=/home/user/install/apache-tomcat-6.0.20/
export DRMAA_LIBRARY_PATH=/opt/gridengine/lib/lx26-amd64/libdrmaa.so
export JAVA_HOME=/home/user/install/java/
export HADOOP_HOME=/home/user/install/hadoop/
export HADOOP_CLASSPATH=/home/user/install/hadoop/lib/

$> nmap -v 서버아이피

예)

$> nmap -v ftp.kaist.ac.kr

Starting Nmap 4.11 ( http://www.insecure.org/nmap/ ) at 2012-09-24 15:57 KST

DNS resolution of 1 IPs took 6.50s.

Initiating SYN Stealth Scan against ftp.kaist.ac.kr (143.248.234.110) [1680 ports] at 15:57

Discovered open port 21/tcp on 143.248.234.110

The SYN Stealth Scan took 23.95s to scan 1680 total ports.

Host ftp.kaist.ac.kr (143.248.234.110) appears to be up ... good.

Interesting ports on ftp.kaist.ac.kr (143.248.234.110):

Not shown: 1679 filtered ports

PORT   STATE SERVICE

21/tcp open  ftp

 

Nmap finished: 1 IP address (1 host up) scanned in 30.569 seconds

               Raw packets sent: 3365 (148.040KB) | Rcvd: 6 (276B)

<아이피 확인>

$> nslookup ftp.kaist.ac.kr

예)

$> nslookup ftp.kaist.ac.kr

Server:     203.241.132.34

Address:    203.241.132.34#53

 

Non-authoritative answer:

Name:   ftp.kaist.ac.kr

Address: 143.248.234.110