merge of 00b67a11e33c3ed390556805ed6d1078528bee70DROPBEAR_0.44test2

     and 42c7bdf484b16e279a0f68604a4346d8fa5ed70c

1 files changed, 16 insertions, 1 deletions

diff --git a/README b/README
index 5dc3a44..52e3cf0 100644
--- a/README
+++ b/README
@@ -17,7 +17,7 @@ matt@ucc.asn.au
 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 @@ OpenSSH sshd manpage, and will not allow a login for these keys.
 
 ============================================================================
 
+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.