#Asus merlin dropbear ssh key android

Is there anything I'm missing? At this point, I think my only option would be to extract the dropbear's private key from /etc/dropbear/dropbear_rsa_host_key and use it instead of generating my own. I also tried everything from scratch, after resetting the router to the factory settings, with the same result. I tried both root and admin as the SSH user. The key is saved via the router's Web UI in the correct format (i.e., ssh-rsa AAAA.5iYw= rsa-key-20180401, no line breaks).

#Asus merlin dropbear ssh key android

The permission for ~/.ssh folder is set to 700, for ~/.ssh/authorized_keys to 600. To be more exact: On the PC you need to have (and use): /.ssh/idrsa (private key) On Android you need to have just the public key: /data/dropbear/.ssh/authorizedkeys (which should be identical to the /.ssh/idrsa.pub on your pc). I know it's that one by running dropbearkey -y -f /etc/dropbear/dropbear_rsa_host_key. When I go to '/etc/dropbear', I see three files: dropbeardsshostkey, dropbearecdsahostkey and dropbearrsahostkey. I expect it to be my key from ~/.ssh/authorized_keys but instead I'm always seeing the dropbear's own public key (from /etc/dropbear/dropbear_rsa_host_key). Im a noob with certs, but my understanding is that if I have SSH setup right, I shouldnt see this prompt. As PUTTY negotiates the session encryption, it prompts to accept the public key provided by the server. I use PUTTYGEN to generate a pair of RSA-2048 keys, save the public key at ~/.ssh/authorized_keys on the router, then try to connect with PUTTY, which I've limited to RSA only. Having read many posts and howtos (including this one), I still can't get it working. With this, you can just run ssh_github instead of ssh and it will connect even if there is no known_hosts file where you put the script.I'm trying to enable passwordless SSH login on my ASUS RT-AC68U home router which runs version 384.4_2 of Asuswrt-Merlin firmware (the most recent one at the time of posting this). Ssh -o 'UserKnownHostsFile $TEMPFILE' $TEMPFILE ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAq2A7hRGmdnm9tUDbO9IDSwBK6TbQa+ PXYPCPy6rbTrTtw7PHkccKrpp0yVhp5HdEIcKr6pLlVDBfOLX9QUsењњOV0wzfjIJNlGEYsdlLJizHhbn2mUjvSAHQqZETYP81eFzLQNnPHt4EVVUh7VfDESU84KezmD5QlWpXLmvU31/yMf+Se8xhHTvKSCZIFImWwoG6mbUoWf9nzpIoaSjB+weqqUUmpaaasXVal72J+UX2B+ 2RPW3RcT0eOzQgqlJе…ѓRKrTJvdsjE3JEAvGq3lGHSZXy28G3skua2SmVi/w4ењњE6gbODqnTWlg7+wC604ydGXA8VJiS5ap43JXiUFFAaQ=' HOSTKEY=' ssh-dss AAAAB3NzaC1kc3MAAACBANGFW2P9xlGU3zWrymJgI/lKo//ZW2WfVtmbsUZJ5uyKArtlQOT2+WRhcg4979aFxgKdcsqAYW3/LS1T2km3jYW/vr4Uzn+dXWODVk5VlUiZ1HFOHf6s6ITcZvjvdbp6ZbpM+DuJT7Bw+ h5Fx8Qt8I16oCZYmAPJRtu46o9C2zk1AAAAFQC4gdFGcSbp5Gr0Wd5Ay/jtcldMewAAAIATTgn4sY4Nem/FQE+XJlyUQptPWMem5fwOcWtSXiTKaaN0lkk2p2snz+EJvAGXGq9dTSWHyLJSM2W6ZdQDqWJ1k+cL8CARAqL+UMwF84CR0m3hj+wtVGD/J4G5kW2DBAf4/bqzP4469lT+dF2FRQ2L9JKXrCWcnhMtJUvua8dvnwAAAIB6C4nQfAA7x8oLta6tT+oCk2WQcydNsyugE8vLrHlogoWEicla6cWPk7oXSspbzUcfkjN3Qa6e74PhRkc7JdSdAlFzU3m7LMkXo1MHgkqNX8glxWNVqBSc0YRdbFdTkL0C6gtpklilhvuHQCdbgB3LBAikcRkDp+FCVkUgPC/7Rw= The example below is a script, which can be called ssh_github: #!/bin/bash Inside there, place the authorizedkeys file owned by bob with 600 permissions. ssh directory (just like root has) owned by bob with 700 permissions. In the new users home directory (/mnt/bob) make an. Then you can forge a script to save it to a temporary file and use the UserKnownHostsFile option. Dont put your ssh key in the web interface, that is only for the root user. ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAq2A7hRGmdnm9tUDbO9IDSwBK6TbQa+PXYPCPy6rbTrTtw7PHkccKrpp0yVhp5HdEIcKr6pLlVDBfOLX9QUsењњOV0wzfjIJNlGEYsdlLJizHhbn2mUjvSAHQqZETYP81eFzLQNnPHt4EVVUh7VfDESU84KezmD5QlWpXLmvU31/yMf+Se8xhHTvKSCZIFImWwoG6mbUoWf9nzpIoaSjB+weqqUUmpaaasXVal72J+UX2B+2RPW3RcT0eOzQgqlJе…ѓRKrTJvdsjE3JEAvGq3lGHSZXy28G3skua2SmVi/w4ењњE6gbODqnTWlg7+wC604ydGXA8VJiS5ap43JXiUFFAaQ= ssh-dss AAAAB3NzaC1kc3MAAACBANGFW2P9xlGU3zWrymJgI/lKo//ZW2WfVtmbsUZJ5uyKArtlQOT2+WRhcg4979aFxgKdcsqAYW3/LS1T2km3jYW/vr4Uzn+dXWODVk5VlUiZ1HFOHf6s6ITcZvjvdbp6ZbpM+DuJT7Bw+h5Fx8Qt8I16oCZYmAPJRtu46o9C2zk1AAAAFQC4gdFGcSbp5Gr0Wd5Ay/jtcldMewAAAIATTgn4sY4Nem/FQE+XJlyUQptPWMem5fwOcWtSXiTKaaN0lkk2p2snz+EJvAGXGq9dTSWHyLJSM2W6ZdQDqWJ1k+cL8CARAqL+UMwF84CR0m3hj+wtVGD/J4G5kW2DBAf4/bqzP4469lT+dF2FRQ2L9JKXrCWcnhMtJUvua8dvnwAAAIB6C4nQfAA7x8oLta6tT+oCk2WQcydNsyugE8vLrHlogoWEicla6cWPk7oXSspbzUcfkjN3Qa6e74PhRkc7JdSdAlFzU3m7LMkXo1MHgkqNX8glxWNVqBSc0YRdbFdTkL0C6gtpklilhvuHQCdbgB3LBAikcRkDp+FCVkUgPC/7Rw= Example: $ ssh-keyscan -t rsa,dsa 2>/dev/null If what you want is to be able to use programmatically AND avoid Man-In-The-Middle attack, then I suggest you get the known fingerprint using the command ssh-keyscan. The first time you ssh into your router, you will probably see a warning about the RSA key. To ssh into your router, you can enter the following command in a terminal emulator using you routers LAN IP address that is typically 192.168.1.1 : ssh root 192.168.1.1. Using SSH Programmatically with known hosts key OpenWrt listens for incoming SSH connections on port 22/tcp by default.