|
|
|
|
|
À̸§ : È£¼® (211.¢½.74.31) |
|
³¯Â¥ : 2005-07-29 15:06:23 |
|
Á¦¸ñ : scp ÀÇ ¼³Á¤ ¹æ¹ý db-zone |
|
------¿øº»¸Þ¼¼Áö------
º¸³½»ç¶÷: yun9598@hanmail.net
¹Þ´Â»ç¶÷: hiweb@drimhitech.com
³¯Â¥: 2005-07-28 20:00:08
Á¦¸ñ: Æнº¿öµå ¾øÀÌ slogin setting ¹æ¹ý ÀÔ´Ï´Ù.
¾È³çÇϼ¼¿ä.
µðºñÁ¸ÀÇ À±Å¼·ÀÔ´Ï´Ù.
Æнº¿öµå ¾øÀÌ slogin setting ¹æ¹ý
1. Oracle °èÁ¤¿¡¼
a. Generate the user's public and private SSH keys (~/.ssh/id_dsa.pub
and id_dsa), as the oracle user:
$ ssh-keygen -t dsa
i. "Enter file in which to save the key ...:" --> Press ENTER.
ii. "Enter passphrase ...:"
For LESS Secure connection just Press ENTER.
For Secure connection enter a passphrase only you will know.
iii. "Enter same passphrase again:" Either ENTER or passphrase.
Note: In a real multi-server environment, you would repeat step 'a.'
above on each server in the cluster before proceeding to step 'b.'
b. Create the authorized_keys file by combining the contents of the
id_dsa.pub files from each server. You can do this all on one node
by running the command below multiple times, replacing "raclinux1"
with a different node name each time. As the oracle user:
$ ssh raclinux1 "cat ~/.ssh/id_dsa.pub" >> ~/.ssh/authorized_keys
i. Each time you connect from any node to a new hostname for the first
time, you will see a message similar to:
"The authenticity of host 'raclinux1 (192.168.203.11)' can't be
established. RSA key fingerprint is ...
Are you sure you want to continue connecting (yes/no)?"
Type "yes" and press ENTER. You will then see the message:
"Warning: Permanently added 'raclinux1,192.168.203.11' (RSA) to
the list of known hosts."
ii. "oracle@raclinux1's password:" --> Type "oracle" and press ENTER.
| |
|
|
|
|