From 078d8e27e079bb9568d632a33ef5a369d49c9c1d Mon Sep 17 00:00:00 2001 From: ivan Date: Sun, 30 Jun 2002 01:18:37 +0000 Subject: adding --- httemplate/docs/ssh.html | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100755 httemplate/docs/ssh.html (limited to 'httemplate/docs/ssh.html') diff --git a/httemplate/docs/ssh.html b/httemplate/docs/ssh.html new file mode 100755 index 000000000..5503a242e --- /dev/null +++ b/httemplate/docs/ssh.html @@ -0,0 +1,15 @@ + + Unattended SSH + + +

Unattended SSH

+
Unattended remote login - Freeside can login to remote machines unattended using SSH. This can pose a security risk if not configured correctly, and will allow an intruder who breaks into your freeside machine full access to your remote machines. Do not use this feature unless you understand what you are doing! +

As the freeside user (on your freeside machine), generate an authentication key using ssh-keygen. Since this is for unattended operation, use a blank passphrase. +
Append the newly-created identity.pub file to ~root/.ssh/authorized_keys on the remote machine(s). +
Some new SSH v2 implementation accept v2 style keys only. Use the -t option to ssh-keygen, and append the created id_dsa.pub or id_rsa.pub to ~root/.ssh/authorized_keys2 on the remote machine(s). +
You may need to set PermitRootLogin without-password (meaning with keys only) in your sshd_config file on the remote machine(s). +

+ + + -- cgit v1.2.1 From ed0c10c5969c60fd2be050a9a5f3830bc347739a Mon Sep 17 00:00:00 2001 From: ivan Date: Mon, 9 Sep 2002 19:54:00 +0000 Subject: doc clarification about users --- httemplate/docs/ssh.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'httemplate/docs/ssh.html') diff --git a/httemplate/docs/ssh.html b/httemplate/docs/ssh.html index 5503a242e..9716f1e86 100755 --- a/httemplate/docs/ssh.html +++ b/httemplate/docs/ssh.html @@ -6,8 +6,8 @@
Unattended remote login - Freeside can login to remote machines unattended using SSH. This can pose a security risk if not configured correctly, and will allow an intruder who breaks into your freeside machine full access to your remote machines. Do not use this feature unless you understand what you are doing!

As the freeside user (on your freeside machine), generate an authentication key using ssh-keygen. Since this is for unattended operation, use a blank passphrase. -
Append the newly-created identity.pub file to ~root/.ssh/authorized_keys on the remote machine(s). -
Some new SSH v2 implementation accept v2 style keys only. Use the -t option to ssh-keygen, and append the created id_dsa.pub or id_rsa.pub to ~root/.ssh/authorized_keys2 on the remote machine(s). +
Append the newly-created identity.pub file to ~root/.ssh/authorized_keys (or the appopriate ~username/.ssh/authorized_keys) on the remote machine(s). +
Some new SSH v2 implementation accept v2 style keys only. Use the -t option to ssh-keygen, and append the created id_dsa.pub or id_rsa.pub to ~root/.ssh/authorized_keys2 (or the appopriate ~username/.ssh/authorized_keys) on the remote machine(s).
You may need to set PermitRootLogin without-password (meaning with keys only) in your sshd_config file on the remote machine(s).

-- cgit v1.2.1 From e58e375c39f08c28239ecc173cc3fbf3f5ca5b92 Mon Sep 17 00:00:00 2001 From: ivan Date: Fri, 30 May 2003 08:45:33 +0000 Subject: doc --- httemplate/docs/ssh.html | 1 + 1 file changed, 1 insertion(+) (limited to 'httemplate/docs/ssh.html') diff --git a/httemplate/docs/ssh.html b/httemplate/docs/ssh.html index 9716f1e86..d2c501e35 100755 --- a/httemplate/docs/ssh.html +++ b/httemplate/docs/ssh.html @@ -9,6 +9,7 @@

Append the newly-created identity.pub file to ~root/.ssh/authorized_keys (or the appopriate ~username/.ssh/authorized_keys) on the remote machine(s).

Some new SSH v2 implementation accept v2 style keys only. Use the -t option to ssh-keygen, and append the created id_dsa.pub or id_rsa.pub to ~root/.ssh/authorized_keys2 (or the appopriate ~username/.ssh/authorized_keys) on the remote machine(s).

You may need to set PermitRootLogin without-password (meaning with keys only) in your sshd_config file on the remote machine(s). +

You may want to set ForwardX11 = no in ~root/.ssh/config to prevent spurious errors if your distribution turns on X11 forwarding by default. -- cgit v1.2.1