diff options
author | Daniel Kahn Gillmor <dkg@fifthhorseman.net> | 2008-08-21 01:57:00 -0400 |
---|---|---|
committer | Daniel Kahn Gillmor <dkg@fifthhorseman.net> | 2008-08-21 01:57:00 -0400 |
commit | c0fed884906cc1a55f447449d323e96397952ee9 (patch) | |
tree | eeec96e33a2f6b4664774aa2b6087631a3b73d80 /website/bugs/install-seckey2sshagent-in-usr-bin.mdwn | |
parent | 3c65d3d8ce819bc94cce81724f0374765e405906 (diff) |
updating documentation (incl. debian/changelog) to reflect new subkey-to-ssh-agent subcommand.
Diffstat (limited to 'website/bugs/install-seckey2sshagent-in-usr-bin.mdwn')
-rw-r--r-- | website/bugs/install-seckey2sshagent-in-usr-bin.mdwn | 10 |
1 files changed, 9 insertions, 1 deletions
diff --git a/website/bugs/install-seckey2sshagent-in-usr-bin.mdwn b/website/bugs/install-seckey2sshagent-in-usr-bin.mdwn index 0163727..e2c2682 100644 --- a/website/bugs/install-seckey2sshagent-in-usr-bin.mdwn +++ b/website/bugs/install-seckey2sshagent-in-usr-bin.mdwn @@ -35,9 +35,17 @@ 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 |