Revision history [back]

I just updated to 1.1.4.29 which overall seems to have gone ok. I did encounter a strange side effect, though: After the update, I was no longer able to use ssh to connect to the Jolla. I then tried to restart sshd from a terminal, I got an error message in the log:

May 10 00:03:25 Jolla systemd[1]: Started OpenSSH server daemon.
May 10 00:03:25 Jolla sshd[2731]: /etc/ssh/sshd_config line 110: Bad yes/no argument: sandbox
May 10 00:03:25 Jolla systemd[1]: sshd.service: main process exited, code=exited, status=255/n/a
May 10 00:03:25 Jolla systemd[1]: Unit sshd.service entered failed state.
May 10 00:03:26 Jolla systemd[1]: sshd.service holdoff time over, scheduling restart.
May 10 00:03:26 Jolla systemd[1]: sshd.service start request repeated too quickly, refusing to start.
May 10 00:03:26 Jolla systemd[1]: Unit sshd.service entered failed state.

I proceeded to modify /etc/ssh/sshd_config and changed the line

UsePrivilegeSeparation sandbox

to

UsePrivilegeSeparation yes

After that change, sshd started normally and I could use ssh again to connect to the Jolla. I just don't have any idea why this occurred - as far as I remember I was running stock sshd before the update.

I just updated to 1.1.4.29 which overall seems to have gone ok. I did encounter a strange side effect, though: After the update, I was no longer able to use ssh to connect to the Jolla. I then tried to restart sshd from a terminal, I got an error message in the log:

May 10 00:03:25 Jolla systemd[1]: Started OpenSSH server daemon.
May 10 00:03:25 Jolla sshd[2731]: /etc/ssh/sshd_config line 110: Bad yes/no argument: sandbox
May 10 00:03:25 Jolla systemd[1]: sshd.service: main process exited, code=exited, status=255/n/a
May 10 00:03:25 Jolla systemd[1]: Unit sshd.service entered failed state.
May 10 00:03:26 Jolla systemd[1]: sshd.service holdoff time over, scheduling restart.
May 10 00:03:26 Jolla systemd[1]: sshd.service start request repeated too quickly, refusing to start.
May 10 00:03:26 Jolla systemd[1]: Unit sshd.service entered failed state.

I proceeded to modify /etc/ssh/sshd_config and changed the line

UsePrivilegeSeparation sandbox

to

UsePrivilegeSeparation yes

After that change, sshd started normally and I could use ssh again to connect to the Jolla. I just don't have any idea why this occurred - as far as I remember I was running stock sshd before the update.

I just updated to 1.1.4.29 which overall seems to have gone ok. I did encounter a strange side effect, though: After the update, I was no longer able to use ssh to connect to the Jolla. I then tried to restart sshd from a terminal, I got an error message in the log:

May 10 00:03:25 Jolla systemd[1]: Started OpenSSH server daemon.
May 10 00:03:25 Jolla sshd[2731]: /etc/ssh/sshd_config line 110: Bad yes/no argument: sandbox
May 10 00:03:25 Jolla systemd[1]: sshd.service: main process exited, code=exited, status=255/n/a
May 10 00:03:25 Jolla systemd[1]: Unit sshd.service entered failed state.
May 10 00:03:26 Jolla systemd[1]: sshd.service holdoff time over, scheduling restart.
May 10 00:03:26 Jolla systemd[1]: sshd.service start request repeated too quickly, refusing to start.
May 10 00:03:26 Jolla systemd[1]: Unit sshd.service entered failed state.

I proceeded to modify /etc/ssh/sshd_config and changed the line

UsePrivilegeSeparation sandbox

to

UsePrivilegeSeparation yes

After that change, sshd started normally and I could use ssh again to connect to the Jolla. I just don't have any idea why this occurred - as far as I remember I was running stock sshd before the update.

I just updated to 1.1.4.29 which overall seems to have gone ok. I did encounter a strange side effect, though: After the update, I was no longer able to use ssh to connect to the Jolla. I then tried to restart sshd from a terminal, I got an error message in the log:

May 10 00:03:25 Jolla systemd[1]: Started OpenSSH server daemon.
May 10 00:03:25 Jolla sshd[2731]: /etc/ssh/sshd_config line 110: Bad yes/no argument: sandbox
May 10 00:03:25 Jolla systemd[1]: sshd.service: main process exited, code=exited, status=255/n/a
May 10 00:03:25 Jolla systemd[1]: Unit sshd.service entered failed state.
May 10 00:03:26 Jolla systemd[1]: sshd.service holdoff time over, scheduling restart.
May 10 00:03:26 Jolla systemd[1]: sshd.service start request repeated too quickly, refusing to start.
May 10 00:03:26 Jolla systemd[1]: Unit sshd.service entered failed state.

I proceeded to modify /etc/ssh/sshd_config and changed the line

UsePrivilegeSeparation sandbox

to

UsePrivilegeSeparation yes

After that change, sshd started normally and I could use ssh again to connect to the Jolla. I just don't have any idea why this occurred - as far as I remember I was running stock sshd before the update.