summaryrefslogtreecommitdiff
path: root/public_hurd_boxen.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'public_hurd_boxen.mdwn')
-rw-r--r--public_hurd_boxen.mdwn28
1 files changed, 16 insertions, 12 deletions
diff --git a/public_hurd_boxen.mdwn b/public_hurd_boxen.mdwn
index 8ac12799..54694f35 100644
--- a/public_hurd_boxen.mdwn
+++ b/public_hurd_boxen.mdwn
@@ -12,27 +12,25 @@ is included in the section entitled
Here are some Hurd boxes that users have made available to the public:
[[!table class="table_style_1" data="""
-"Host Name","Operator","Access","Distro","Machine Specs","Comments"
-"flubber.bddebian.com","[[Barry_de_Freese|bddebian]]","ssh; port 2250","Debian","Celeron; 2.2 GHz; 666 MiB","domU on zenhost"
-"foobar.bddebian.com","[[Barry_de_Freese|bddebian]]","internal","Debian","Celeron; 2.2 GHz; 160 MiB","domU on zenhost; web server"
-"clubber.bddebian.com","[[Barry_de_Freese|bddebian]]","ssh; port 2251","Debian","PIII 1 GHz; 384 MiB"
-"gnubber.bddebian.com","[[Barry_de_Freese|bddebian]]","ssh; port 2254","Debian","PII 733 MHz; 384 MiB"
-"goober.bddebian.com","[[Barry_de_Freese|bddebian]]","ssh; port 2255","Debian","?"
+"Hoster","Name","Distribution","Machine Specs","Comments"
+"bddebian","clubber","Debian GNU/Hurd","PIII 1 GHz; 384 MiB"
+"bddebian","flubber","Debian GNU/Hurd","Celeron 2.2 GHz; 666 MiB","Xen domU on zenhost"
+"bddebian","foobar","Debian GNU/Hurd","Celeron 2.2 GHz; 160 MiB","Xen domU on zenhost; web server"
+"bddebian","gnubber","Debian GNU/Hurd","PII 733 MHz; 384 MiB"
+"bddebian","goober","Debian GNU/Hurd","?"
"""]]
-To request an account on the `*.bddebian.com` machines either contact
+To request an account on the *bddebian* machines either contact
*bddebian* or *tschwinge* (other people might also be able to help) in [[IRC]]
or send email to <hurd-shell-account@gnu.org>. Also use these contact
addresses for requesting support with respect to software installations, etc.
-To be able to use just `ssh [machine]`, you should append your public SSH key
+For easy access, you should append your public SSH key(s)
to `~/.ssh/authorized_keys` on the remote machine.
-And if you don't want to worry about the machines's IP addresses changing (due
-to dial-up connection) or the host keys changing every now and then (when the
-machines are re-installed), put something like the following into
-`~/.ssh/config` of the machine you connect from:
+Also, add the following stanza to `~/.ssh/config` of the machine you're
+connecting from:
Host clubber.bddebian.com clubber
HostName clubber.bddebian.com
@@ -55,3 +53,9 @@ machines are re-installed), put something like the following into
UserKnownHostsFile /dev/null
StrictHostKeyChecking no
User [username]
+
+The `CheckHostIP` statement is for not having to worry about the machines's IP
+addresses changing (due to dial-up connection), and the `UserKnownHostsFile`
+one together with the `StrictHostKeyChecking` one are for not having ot worry
+about the host keys changing (when the machines are re-installed). Of course,
+this undermines SSH's security system, so you may disagree about these.