Mercurial > dropbear
changeset 874:68e2a0f6c1ef
Update README
| author | Matt Johnston <matt@ucc.asn.au> |
|---|---|
| date | Tue, 03 Dec 2013 21:03:23 +0800 |
| parents | 17b15683648d |
| children | 6c7a15668d5a |
| files | README |
| diffstat | 1 files changed, 7 insertions(+), 3 deletions(-) [+] |
line wrap: on
line diff
--- a/README Tue Dec 03 20:59:03 2013 +0800 +++ b/README Tue Dec 03 21:03:23 2013 +0800 @@ -42,8 +42,7 @@ 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. +Dropbear does not support encrypted hostkeys though can connect to ssh-agent. ============================================================================ @@ -52,13 +51,18 @@ ============================================================================ -To run the server, you need to generate server keys, this is one-off: +To run the server, you need to server keys, this is one-off: ./dropbearkey -t rsa -f dropbear_rsa_host_key ./dropbearkey -t dss -f dropbear_dss_host_key +./dropbearkey -t ecdsa -f dropbear_dss_host_key or alternatively convert OpenSSH keys to Dropbear: ./dropbearconvert openssh dropbear /etc/ssh/ssh_host_dsa_key dropbear_dss_host_key +You can also get Dropbear to create keys when the first connection is made - +this is preferable to generating keys when the system boots. Make sure +/etc/dropbear/ exists and then pass '-R' to the dropbear server. + ============================================================================ If the server is run as non-root, you most likely won't be able to allocate a