Comments to bugs.

3 files changed, 29 insertions, 2 deletions

diff --git a/website/bugs/install-seckey2sshagent-in-usr-bin.mdwn b/website/bugs/install-seckey2sshagent-in-usr-bin.mdwn
index 345b71f..8044ce5 100644
--- a/website/bugs/install-seckey2sshagent-in-usr-bin.mdwn
+++ b/website/bugs/install-seckey2sshagent-in-usr-bin.mdwn
@@ -2,3 +2,11 @@
 
 I know it's a hack - but installing seckey2sshagent in /usr/bin/ would make it
 much easier for people to use. 
+
+---
+
+I'm not sure I really want to include this hack with the debs.  It's really not useful for any kind of regular use.  I would rather focus on getting openpgp2ssh to support passprotected keys.
+
+As another possibility, I was planning on modifying the script so that it could export to a passprotected file.  I think this would be a lot more useful.  Let me get that working, then let's revist the issue of including it in the packaging.
+
+-- Big Jimmy.
diff --git a/website/bugs/monkeysphere-ignores-HashKnownHosts-directive.mdwn b/website/bugs/monkeysphere-ignores-HashKnownHosts-directive.mdwn
index 4ad4918..0f6654c 100644
--- a/website/bugs/monkeysphere-ignores-HashKnownHosts-directive.mdwn
+++ b/website/bugs/monkeysphere-ignores-HashKnownHosts-directive.mdwn
@@ -9,5 +9,16 @@ instead of in the clear.
 fwiw: i'm using OpenSSH 5.1p1 on a debian lenny system (backported
 from sid)
 
-> I can confirm this too (I'm running openssh-client 1:4.7p1-12) -- Jamie (Jam
-> Jam)
+---
+
+I can confirm this too (I'm running openssh-client 1:4.7p1-12)
+
+-- Jamie (Jam Jam)
+
+---
+
+There is absolutely no attempt by any monkeysphere utility to parse
+any ssh or sshd config file.  This will probably need to be delt with
+down the line, but it's not a particular easy task at the moment.
+
+-- Big Jimmy.
diff --git a/website/bugs/setup-test-server-for-public.mdwn b/website/bugs/setup-test-server-for-public.mdwn
index 3e4c4df..ca647cb 100644
--- a/website/bugs/setup-test-server-for-public.mdwn
+++ b/website/bugs/setup-test-server-for-public.mdwn
@@ -5,3 +5,11 @@ test it with a participating server as soon as they've finished setting things
 up. Minimally - just testing the acceptance of the server's identity would be
 great.
 
+---
+
+I guess we don't really want to use george for this purpose?  Does
+someone have a spare virtual machine that we could use for this
+purpose?  The test machine wouldn't actually have to do any user
+authentication, I guess.
+
+-- Big Jimmy.