![]() ![]() If you wish to SSH from the OpenWRT device, Dropbear needs the keys in a different format to OpenSSH so a different program is used:ĭropbearkey -f ~ /.ssh /id_dropbear -t rsa -s 2048īy default Dropbear reads ~/.ssh/id_dropbear so putting the private key there may avoid the need to create an SSH configuration file. # Generate a new key pair, 3072-bit RSA by default ssh-keygen # Generate a new Ed25519 key pair ssh-keygen -t ed25519 After you have used this utility, you will have two files, by default ~/.ssh/id_ (the private key) and ~/.ssh/id_.pub (the public key). The ssh-keygen utility can be used to generate a key pair to use for authentication. So why is my config file not working on the OpenWrt? Does Dropbear not know anything about ~/.Skip this if you already have a public / private key pair on your client machine that you intend to use to connect to the OpenWrt SSH server. I set up a ~/.ssh/config file on the other host as above, except I use an open-ssh client on that host, and can ssh from it to OpenWrt like this: # ssh openwrt Name does not resolveĪctually I get the same error even if I change the Port to 1022 even though the sshd on the remote host is also listening on that port. Ssh: Connection to exited: Connect failed: Error resolving 'ncp' port '22'. I also made a ~/.ssh/config file on the OpenWrt host like this: Host ncpīut when I try to ssh now with this command: # ssh ncp Now I can ssh from OpenWrt to the other host like this: # ssh -i ncp_key_dropbear -p 22 I converted the private open-ssh key of the other host to dropbear format and saved it to ~/.ssh/ncp_key_dropbear on the OpenWrt host. I want to ssh from one host (OpenWrt running Dropbear) to another host on the same LAN that is running open-ssh server and client. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |