![]() rw-r-r- 1 root root 565 Apr 17 23:11 id_rsa.pubĪfter seeing "Begin: Starting dropbear. rw- 1 root root 805 Apr 17 21:33 dropbear_rsa_host_key rw- 1 root root 140 Apr 17 21:33 dropbear_ecdsa_host_key ![]() rw- 1 root root 458 Apr 17 21:33 dropbear_dss_host_key ![]() rw- 1 root root 565 Apr 17 23:11 authorized_keys etc/dropbear-initramfs/authorized_keys: ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQCi3gJaNC89jJSdzlD/qxjwzKC33PpERqpyt7q2PIHFM7hoDk7M/MU9/5k+jmIy80Xt0ZvswLdxAi4p26wr+13vtwNHJIdsLdswCNmKxz+nyBvIw2g/pT7I3368B6KZ1MKokQ4Nz4HQu5WuEDZXTZSnsvP/7n732+zwhFZDPz+NZ4HdY0cveTeb6hW+peZEe3xCBQ4PeGNaH1U+VTuNveyAnFP圎jHvQhG39CtAn4SAEYd7UMNmyVFWDf2+ymlgWRwq2joAQKg/vB4qrdwX6MWEPf0r0H2jtnm+y8ZFrEdmjJTWmUKhliE928Oc63exAPaGmwJ4+tjrSUU0twHe+v9HnTrMiJHvOUQDoUuMsyqsO5auo3RNUMXMKEhA/tJbZjpAMj5wMtdcvHJ0u5VJ/oZQavm0uYUBAhOc94JUr6qRVfNk1PbCGgBx1hCfIKORVHz05bsMZUYeUaruhfMGg3jGTpfojgBRWZ0gbQTnEaxNcXeZnSEoTmX8jOhSsOmhqjU= -la /etc/dropbear-initramfs shows: drwxr-xr-x 2 root root 4096 Apr 17 23:11. Here is how I have it set up on the server: After running update-initramfs -u, I still am not able to connect with Dropbear. In /etc/dropbear-initramfs/authorized_keys I have the public key, and on my client machine I have the keypair in the /home//.ssh/ directory. It's 300+ lines of (now flawed) shell script to do the same thing that one fairly simple ssh command can do (or one very very simple scp, plus one very very simple cat command on the server).I've create a RSA key pair with ssh-keygen. It doesn't do much that you couldn't do pretty easily without it. I've always found the script a bit silly and mostly pointless. though I highly doubt this as the flawed-syntax used should not be valid in any POSIX shell.Īnother lazy way would be - as noted above - just don't use this script. This makes me wonder if I am missing something about how this code may work on a BSD system but not linux. Though I am a bit concerned about this - from my perspective this seems like a glaring and ridiculously obvious error which is not to be expected from the development team behing this package. The lazy way would be to wait for it to be included from upstream in an upcoming version of the package. The smart way would just be to modify the installed file as it's just moving one closing parenthesis in a shell script. The "right way" might be to retrieve the source code with abs, making the change, then rebuilding the package.
0 Comments
Leave a Reply. |