1 [[meta title="Install seckey2sshagent in /usr/bin/"]]
3 I know it's a hack - but installing seckey2sshagent in /usr/bin/ would make it
4 much easier for people to use.
8 I'm not sure I really want to include this hack with the debs. It's
9 really not useful for any kind of regular use. I would rather focus
10 on getting openpgp2ssh to support passprotected keys.
12 As another possibility, I was planning on modifying the script so that
13 it could export to a passprotected file. I think this would be a lot
14 more useful. Let me get that working, then let's revist the issue of
15 including it in the packaging.
21 Ok - sounds good to me. I'm thinking in terms of getting other people to try
22 out the Monkeysphere - maybe the README should just say: we're only half
23 done. You can verify the identity of servers, but we haven't completed the
24 part about verifying you to a server. Then it could say: if you're really
25 interested, you can run this hacky script but we make no guarantees.
31 I just realized that i think i can test for the presence of [GNU-dummy
33 GnuTLS](http://lists.gnu.org/archive/html/gnutls-devel/2008-08/msg00005.html),
34 which means that we can cleanly test whether the proposed [handling of
35 passphrase-locked secret
36 keys](bugs/handle-passphrase-locked-secret-keys/) is functional. With
37 that in mind, I'd like to propose that we could resolve this bug
38 simply by adding a new subcommand: `monkeysphere subkey-to-ssh-agent`,
39 which would fail in the absence of a functionally-patched GnuTLS.
41 Would this proposal be sufficient to resolve this bug?
47 Version 0.11-1 now has the `monkeysphere subkey-to-ssh-agent`
48 subcommand, which works cleanly in the presence of a
49 functionally-patched GnuTLS.