Mercurial > dropbear
comparison 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 |
comparison
equal
deleted
inserted
replaced
87:680a0bc9df0a | 90:c2ac796b130e |
---|---|
15 | 15 |
16 | 16 |
17 In the absence of detailed documentation, some notes follow: | 17 In the absence of detailed documentation, some notes follow: |
18 ============================================================================ | 18 ============================================================================ |
19 | 19 |
20 Public key auth: | 20 Server public key auth: |
21 | 21 |
22 You can use ~/.ssh/authorized_keys in the same way as with OpenSSH, just put | 22 You can use ~/.ssh/authorized_keys in the same way as with OpenSSH, just put |
23 the key entries in that file. They should be of the form: | 23 the key entries in that file. They should be of the form: |
24 | 24 |
25 ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAIEAwVa6M6cGVmUcLl2cFzkxEoJd06Ub4bVDsYrWvXhvUV+ZAM9uGuewZBDoAqNKJxoIn0Hyd0Nk/yU99UVv6NWV/5YSHtnf35LKds56j7cuzoQpFIdjNwdxAN0PCET/MG8qyskG/2IE2DPNIaJ3Wy+Ws4IZEgdJgPlTYUBWWtCWOGc= someone@hostname | 25 ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAIEAwVa6M6cGVmUcLl2cFzkxEoJd06Ub4bVDsYrWvXhvUV+ZAM9uGuewZBDoAqNKJxoIn0Hyd0Nk/yU99UVv6NWV/5YSHtnf35LKds56j7cuzoQpFIdjNwdxAN0PCET/MG8qyskG/2IE2DPNIaJ3Wy+Ws4IZEgdJgPlTYUBWWtCWOGc= someone@hostname |
27 You must make sure that ~/.ssh, and the key file, are only writable by the | 27 You must make sure that ~/.ssh, and the key file, are only writable by the |
28 user. | 28 user. |
29 | 29 |
30 NOTE: Dropbear ignores authorized_keys options such as those described in the | 30 NOTE: Dropbear ignores authorized_keys options such as those described in the |
31 OpenSSH sshd manpage, and will not allow a login for these keys. | 31 OpenSSH sshd manpage, and will not allow a login for these keys. |
32 | |
33 ============================================================================ | |
34 | |
35 Client public key auth: | |
36 | |
37 Dropbear can do public key auth as a client, but you will have to convert | |
38 OpenSSH style keys to Dropbear format, or use dropbearkey to create them. | |
39 | |
40 If you have an OpenSSH-style private key ~/.ssh/id_rsa, you need to do: | |
41 | |
42 dropbearconvert openssh dropbear ~/.ssh/id_rsa ~/.ssh/id_rsa.db | |
43 dbclient -i ~/.ssh/id_rsa.db <hostname> | |
44 | |
45 Currently encrypted keys aren't supported, neither is agent forwarding. At some | |
46 stage both hopefully will be. | |
32 | 47 |
33 ============================================================================ | 48 ============================================================================ |
34 | 49 |
35 If you want to get the public-key portion of a Dropbear private key, look at | 50 If you want to get the public-key portion of a Dropbear private key, look at |
36 dropbearkey's '-y' option. | 51 dropbearkey's '-y' option. |