The unified diff between revisions [83d9a25e..] and [edf8bd91..] is displayed below. It can also be downloaded as a raw diff.

This diff has been restricted to the following files: 'README'

#
#
# patch "README"
#  from [f366e51647a4688cf5c488f4f9d6c0b1c50b8405]
#    to [6701599fcda6970e0addb62d01bbff6c86780e13]
#
============================================================
--- README	f366e51647a4688cf5c488f4f9d6c0b1c50b8405
+++ README	6701599fcda6970e0addb62d01bbff6c86780e13
@@ -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.