diff options
| author | Daniel Kahn Gillmor <dkg@fifthhorseman.net> | 2008-09-02 18:41:29 -0400 |
|---|---|---|
| committer | Daniel Kahn Gillmor <dkg@fifthhorseman.net> | 2008-09-02 18:41:29 -0400 |
| commit | 5475afc7f89d75e9b17394f1dec530acfed29bcc (patch) | |
| tree | b639493625edd1243d5bef8abd8e0bcfdb0abf9c /website | |
| parent | 6576cb269138c36728bb75d3b7242e34aee8a07d (diff) | |
comment on passphrase-less key bug.
Diffstat (limited to 'website')
| -rw-r--r-- | website/bugs/handle-passphrase-locked-secret-keys.mdwn | 20 |
1 files changed, 16 insertions, 4 deletions
diff --git a/website/bugs/handle-passphrase-locked-secret-keys.mdwn b/website/bugs/handle-passphrase-locked-secret-keys.mdwn index bc2a64c..f66bd41 100644 --- a/website/bugs/handle-passphrase-locked-secret-keys.mdwn +++ b/website/bugs/handle-passphrase-locked-secret-keys.mdwn @@ -1,4 +1,4 @@ -[[meta title="MonkeySphere needs to be able to cleanly export passphrase-locked secret keys from the GPG keyring"]] +[[meta title="MonkeySphere can't deal with passphrase-locked primary keys]] At the moment, the only tool we have to export passphrase-locked secret keys from the GPG keyring is `gpg` itself (and `gpg2`, which @@ -100,6 +100,18 @@ Other alternatives? Can this bug be closed? dkg [reported in a comment for a related bug](/bugs/install-seckey2sshagent-in-usr-bin/): - Version 0.11-1 now has the monkeysphere subkey-to-ssh-agent - subcommand, which works cleanly in the presence of a - functionally-patched GnuTLS. + Version 0.11-1 now has the monkeysphere subkey-to-ssh-agent + subcommand, which works cleanly in the presence of a + functionally-patched GnuTLS. + +-------- + +Even with the patched GnuTLS, monkeysphere currently can't currently +deal with passphrase-locked primary keys. I've changed the title of +this bug, but i'd like to keep it open until we are able to deal with +that. The other comments here seem still quite relevant to that +need. + +I've changed the title of this bug to reflect the narrowed scope. + + --dkg |