03-04-2021 04:26 PM
I have a petalinux 2019.1 project that includes packagegroup-core-ssh-dropbear in the rootfs (NOT the normal dropbear package).
I am trying to allow my Putty client to connect to the petalinux system without needing a login, but it is not working.
Every connection attempt is greeted with the login prompt, and it still requires a password. If I disallow password logins, the SSH connection just errors out.
I used Putty key generator to generate my keys. The issue is where do I put them? Varying sources online have suggested that any of the following locations might be the correct place for the key files.
I have tried copying the public key from my Putty client into all of those places, to no avail. Additionally, one source even suggested that only a DSA key would be compatible with non-dropbear SSH clients. This also did not fix the problem.
I believe my main problem is the location of the key. Where is packagegroup-core-ssh-dropbear going to look for authorized keys by default?
03-04-2021 06:57 PM
Interesting problem. Have you seen this: https://forums.xilinx.com/t5/Embedded-Linux/dropbear-root-login-petalinux-2019-1/td-p/979852 (not sure it will help, but it might possibly be related, especially if you're trying to do an ssh root@...)
Out of curiosity, is this better or worse security than a password. Or are you doing it for convenience of a script?
03-05-2021 10:58 AM
Yes, I've seen that thread. It was not useful to me, since the recipe for dropbear is not the same as the recipe for packagegroup-core-ssh-dropbear.
Turning off password logins in SSH is considered better security, since only the systems that have already exchanged keys can SSH to each other. My issue is that process itself.