Prompted for password when connecting by ssh to Batocera despite authorized_keys

garret

I created a new file called 'authorized_keys' in '/userdata/system/ssh'. Inside this file I pasted the public key generated on the client computer which is running linux with openssh.

However, when from the client I give the command:
ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -i /config/.ssh/id_rsa -v root@192.168.XX.XX ls /

I still get asked for the root password of Batocera.

Do you know what I am doing wrong and how to connect without being asked for the root password?

iratash

PubkeyAuthentication should be set to yes in sshd_config. recheck permissions on key file. Google the details.

garret

iratash Sorry could you be more detailed for your answer since I am quite noob.

I have the files 'authorized_keys', 'dropbear_ecdsa_host_key' and 'dropbear_rsa_host_key' all chmod 700 in Batocera.

Where do I find this 'sshd_config' that you are mentioning in Batocera?

iratash

garret Apologies, I'd assumed Batocera used OpenSSH. Haven't worked with Dropbear before, something like this should help:

https://openwrt.org/docs/guide-user/security/dropbear.public-key.auth

garret

iratash

Hmm I did not manage as it seems the structure in Batocera is different.
Is it possible there is no support at all from any devs of Batocera? I would assume it's just a noob request.

Cesium133x

authorized_keys must be located in /userdata/system/.ssh/ (note the . in .ssh), owned by root:root, mode 600:

Also, all its parent directories must not be writable by other users, so /userdata, /userdata/system, and /userdata/system/.ssh must be owned by root:root and mode 755:

# ls -ald /userdata /userdata/system /userdata/system/.ssh /userdata/system/.ssh/authorized_keys
drwxr-xr-x   18 root     root          4096 May 26 11:09 /userdata
drwxr-xr-x   15 root     root          4096 May 26 11:16 /userdata/system
drwx------    2 root     root          4096 May 26 11:16 /userdata/system/.ssh
-rw-------    1 root     root           753 May 26 11:16 /userdata/system/.ssh/authorized_keys

I just got it working today, I had directories owned by user 501.