Merge remote branch 'origin/master'

[monkeysphere.git] / website / bugs / install-seckey2sshagent-in-usr-bin.mdwn

diff --git a/website/bugs/install-seckey2sshagent-in-usr-bin.mdwn b/website/bugs/install-seckey2sshagent-in-usr-bin.mdwn
index 01637276035612ba403bdc07a2bfedcc085626a1..04322a45c38d8a86f674ebba9161610a6ae1ef8f 100644 (file)
--- a/website/bugs/install-seckey2sshagent-in-usr-bin.mdwn
+++ b/website/bugs/install-seckey2sshagent-in-usr-bin.mdwn
@@ -1,4 +1,4 @@
-[[meta title="Install seckey2sshagent in /usr/bin/"]]
+[[!meta title="Install seckey2sshagent in /usr/bin/"]]
 
 I know it's a hack - but installing seckey2sshagent in /usr/bin/ would make it
 much easier for people to use. 
@@ -35,9 +35,25 @@ which means that we can cleanly test whether the proposed [handling of
 passphrase-locked secret
 keys](bugs/handle-passphrase-locked-secret-keys/) is functional.  With
 that in mind, I'd like to propose that we could resolve this bug
-simply by adding a new subcommand: `monkeysphere authkey-to-agent`,
+simply by adding a new subcommand: `monkeysphere subkey-to-ssh-agent`,
 which would fail in the absence of a functionally-patched GnuTLS.
 
 Would this proposal be sufficient to resolve this bug?
 
 --dkg
+
+---
+
+Version 0.11-1 now has the `monkeysphere subkey-to-ssh-agent`
+subcommand, which works cleanly in the presence of a
+functionally-patched GnuTLS.
+
+--dkg
+
+---
+
+I'm marking this bug as [[bugs/done]] - I no longer think we should install
+seckey2sshagent in bin now that we have a clean way of accomplishing that task.
+Nice work dkg!
+
+--sjj