A silent bug fix release, 2023.1.1 [EN / DE]

[towo]

Ich tippe mal einfach auf kaputte Lenovo-Firmware.
Ich habe hier ein Lenovo, das bootet Siduction nicht  im CSM-Mode oder wenn es auf CSM Fist steht.
Ich kann Siduction Live auf der Kiste nur im EFI Mode booten.

[bevo]

@ro_sid habe ich alles schon gemacht.

[raduc]

ssh server seems broken in 2023.1.1, it doesn't start because of missing keys in /etc/ssh:

Code Select Expand


# systemctl start ssh
Job for ssh.service failed because the control process exited with error code.
See "systemctl status ssh.service" and "journalctl -xeu ssh.service" for details.
root@siduction:~# systemctl status ssh
× ssh.service - OpenBSD Secure Shell server
     Loaded: loaded (/lib/systemd/system/ssh.service; disabled; preset: enabled)
     Active: failed (Result: exit-code) since Wed 2023-09-20 02:35:45 UTC; 2s ago
       Docs: man:sshd(8)
             man:sshd_config(5)
    Process: 2333 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=1/FAILURE)
        CPU: 16ms

Sep 20 02:35:45 siduction systemd[1]: ssh.service: Control process exited, code=exited, status=1/FAILURE
Sep 20 02:35:45 siduction systemd[1]: ssh.service: Failed with result 'exit-code'.
Sep 20 02:35:45 siduction systemd[1]: Failed to start ssh.service - OpenBSD Secure Shell server.
Sep 20 02:35:45 siduction systemd[1]: ssh.service: Scheduled restart job, restart counter is at 5.
Sep 20 02:35:45 siduction systemd[1]: ssh.service: Start request repeated too quickly.
Sep 20 02:35:45 siduction systemd[1]: ssh.service: Failed with result 'exit-code'.
Sep 20 02:35:45 siduction systemd[1]: Failed to start ssh.service - OpenBSD Secure Shell server.
root@siduction:~#


Code Select Expand


root@siduction:~# /sbin/sshd -d
debug1: sshd version OpenSSH_9.4, OpenSSL 3.0.10 1 Aug 2023
debug1: Unable to load host key: /etc/ssh/ssh_host_rsa_key
debug1: Unable to load host key: /etc/ssh/ssh_host_ecdsa_key
debug1: Unable to load host key: /etc/ssh/ssh_host_ed25519_key

The only way to fix this is to force reinstall ssh server.

Can the installation media (iso) be fixed for this?

EDIT: Sorry, I added [code] [/code] tags for better reading, hendrikL

[hendrikL]

Mh, well, you can also use our "sshactivate" script, which is located in /usr/sbin.
There is also a "sshdeactivate" script.

Did you try it?

[raduc]

I actually found the same instructions in an old release notes where the sshactivate and sshdeactivate were introduced. However, the manual does not specify it in its SSH section, that should be probably updated. After reading it I thought sshd was already active.

Thanks.

[hendrikL]

@raduc, thank you for that hint, we Will add it to our manual, and for shure to our next release notes again.

If you are familiar with git and GitHub you also can provide improvements via a merge request.
Every user can do. btw.