Mercurial > dropbear
diff README @ 90:c2ac796b130e DROPBEAR_0.44test2
merge of 00b67a11e33c3ed390556805ed6d1078528bee70
and 42c7bdf484b16e279a0f68604a4346d8fa5ed70c
author | Matt Johnston <matt@ucc.asn.au> |
---|---|
date | Sat, 04 Sep 2004 14:19:17 +0000 |
parents | a54d20c96178 |
children | b9d3f725e00b |
line wrap: on
line diff
--- a/README Tue Aug 17 11:14:13 2004 +0000 +++ b/README Sat Sep 04 14:19:17 2004 +0000 @@ -17,7 +17,7 @@ In the absence of detailed documentation, some notes follow: ============================================================================ -Public key auth: +Server public key auth: You can use ~/.ssh/authorized_keys in the same way as with OpenSSH, just put the key entries in that file. They should be of the form: @@ -32,6 +32,21 @@ ============================================================================ +Client public key auth: + +Dropbear can do public key auth as a client, but you will have to convert +OpenSSH style keys to Dropbear format, or use dropbearkey to create them. + +If you have an OpenSSH-style private key ~/.ssh/id_rsa, you need to do: + +dropbearconvert openssh dropbear ~/.ssh/id_rsa ~/.ssh/id_rsa.db +dbclient -i ~/.ssh/id_rsa.db <hostname> + +Currently encrypted keys aren't supported, neither is agent forwarding. At some +stage both hopefully will be. + +============================================================================ + If you want to get the public-key portion of a Dropbear private key, look at dropbearkey's '-y' option.