donsionhudev / droidsshd

Automatically exported from code.google.com/p/droidsshd
0 stars 0 forks source link

Allow Multiple PubKeys #6

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Install a public key.
2. Install another public key.
3. Try to connect using first public key.

What is the expected output? What do you see instead?
I would expect both public keys to have access granted (and another interface 
to be available to revoke keys).  Instead, only the last public key is 
accepted.  This prevents the phone from being accessible from multiple remote 
accounts.

What version of the product are you using? On what operating system?
2010-12-05 (sha1=7ed35d783085a09c04441c34706c2f703e03d795) on Cyanogen 6.1.  
Attempting to connect using OpenSSH on an OpenBSD machine, and on an Ubuntu 
10.10 machine.

Please provide any additional information below.

Original issue reported on code.google.com by Warr1...@gmail.com on 11 Jan 2011 at 4:18

GoogleCodeExporter commented 8 years ago

Original comment by augu...@bott.com.br on 19 Jan 2011 at 11:48

GoogleCodeExporter commented 8 years ago
I was able to work around this by using droidsshd to rsync in a new 
authorized_keys file with multiple keys; dropbear successfully authenticated me 
using any one of the keys in the file.

The UI could be changed to allow a user to individually manage (add/remove) 
keys in the authorized_keys file.

Alternatively, a simpler UI would simply accept an authorized_keys file with 
the keys concatenated, one-per-line, and use it as-is.  All that would need to 
be changed is the validation that rejects files with multiple keys (plus some 
documentation about the feature would be nice).

Original comment by Warr1...@gmail.com on 20 Jan 2011 at 12:18