commiting some bug comments.

[monkeysphere.git] / website / bugs / setup-test-server-for-public.mdwn

diff --git a/website/bugs/setup-test-server-for-public.mdwn b/website/bugs/setup-test-server-for-public.mdwn
index ca647cb9730ec4440b293634d21090028e549305..2ec2a24baf6c3cf7f8be9a615595bba30497ae46 100644 (file)
--- a/website/bugs/setup-test-server-for-public.mdwn
+++ b/website/bugs/setup-test-server-for-public.mdwn
@@ -13,3 +13,41 @@ purpose?  The test machine wouldn't actually have to do any user
 authentication, I guess.
 
 -- Big Jimmy.
+
+---
+
+Maybe we should use George? As you point out - it doesn't actually
+have to do any user authentication. It seems like a waste to have a
+virtual machine that does nothing but deny people's ssh connections.
+And - george is already setup and ready to go.
+-- Sir Jam Jam
+
+---
+
+I like the idea of using George for this.  There's nothing wrong with
+denying people's ssh connections.  Also, we could make public user
+account with limited shells that we could add User IDs that we want to
+encourage to try out the monkeysphere from that perspective.  For
+example, if one of the George admins who is listed as an
+identity-certifier has already certified Foo T. Bar's key, we could
+write a simple note like:
+
+       Dear Foo T. Bar--
+       
+       The user account "foo@george.riseup.net" has been created for
+       you.  You can ssh into it by adding an authentication subkey
+       to your OpenPGP key and publishing it to the public keyservers
+       (or to george.riseup.net).  The easiest way to do this is with
+       the monkeysphere.
+       
+       You can verify george's ssh host key with the monkeysphere
+       before you connect to the host.  Here's how...
+
+--dkg
+
+---
+
+So do we agree that george is doing what we want, and we can therefore
+close this bug?
+
+-- BJ (jgr)