SSHD again… on Lineage OS 17.1

I finally got around to looking into why my rsync automation fails with my new Lineage OS 17.1 device. The old instructions worked like charm. Sshd will start, but the shell user will receive a permission denied after successful authentication.

It turns out that sshd is unhappy with the file ownership or modes for /data. Now I didn’t want to mess with those nor did I want to move the ssh directory to another place so I cheated and told sshd to relax by adding:

StrictModes no

to sshd_config. Probably sshd dislikes that /data is owned by system and not shell nor root – allowing the system user to erase the ssh directory. Seems like one security concept is ruining another…


  1. Hi

    is runuserinit safe to use on LineageOS17 ?

    When I run it I get a message that it was built for an older version of Android and to contact you.

    (Great app BTW – I used it on LineageOS15)

  2. Same reply as to your other post with a bit more detail: Works fine for me on LineageOS 17.1, I think the Android warning just let’s you know that the app might not fully utilize your display depending on the device’s aspect ratio. This warning is generated by the Operating System – not the App itself. Probably I’d have to target a newer Android version, but that might impact backwards compatibility. Currently I have no plans to rebuild the app, let’s see what happens when LOS18.1 is out.

Leave a Reply

Your email address will not be published. Required fields are marked *