From: Rudolf Sykora <rudolf.sykora@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] unix rsa-key with passphrase vs. p9(p)
Date: Fri, 8 Mar 2013 19:02:43 +0100 [thread overview]
Message-ID: <CAOEdRO1aN0nz9XqAN2s2kqBDtrPww3Ead4=SaDmU1rOVvdh4-w@mail.gmail.com> (raw)
On 8 March 2013 17:08, Rudolf Sykora <rudolf.sykora@gmail.com> wrote
> I now see that 9 ssh-agent is really only to deal with passphrases of
> the dsa/rsa keys.
Well, I seem to be wrong again. And have more questions...
In linux, ssh-agent takes care about an (optional) passphrase which
was used to cypher
the public (and perhaps also private, I believe) keys (so that eg the
admin can't abuse these)
generated by ssh-keygen; these keys are usually stored under $HOME/.ssh.
What do I have to do in order to use "9 ssh-agent" (which uses
factotum) when I have
the keys already generated (and their public parts distributed) by
linux's ssh-keygen?
(Ie I have id_rsa and id_rsa.pub in .ssh; and I use a passphrase.)
Particularly, there is some information given in p9p's rsa(1):
----------------
Convert existing Unix SSH version 2 keys instead of generat-
ing new ones:
cd $HOME/.ssh
pemdecode 'DSA PRIVATE KEY' id_dsa | asn12dsa >dsa2
pemdecode 'RSA PRIVATE KEY' id_rsa | asn12rsa >rsa2
Load those keys into factotum:
cat rsa1 rsa2 dsa2 | 9p write -l factotum/ctl
----------------
but my keys are protected with a passphrase, so these commands do not
directly work. What must I do?
Finally, is there any reason to prefer the factotum way rather than the linux's
way just with ssh-keygen (with a passphrase) + ssh-copy-id + (linux's)
ssh-agent?
Thanks!
Ruda
next reply other threads:[~2013-03-08 18:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-08 18:02 Rudolf Sykora [this message]
2013-03-08 18:30 ` Charles Forsyth
2013-03-08 23:27 ` hiro
2013-03-08 23:35 ` Stephen Wiley
2013-03-09 2:09 ` Charles Forsyth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAOEdRO1aN0nz9XqAN2s2kqBDtrPww3Ead4=SaDmU1rOVvdh4-w@mail.gmail.com' \
--to=rudolf.sykora@gmail.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).