On 5/25/24 08:47, Tomasz Torcz wrote:
Dnia Fri, May 24, 2024 at 01:33:44PM +0200, Marius Schwarz napisał(a):
Am 24.05.24 um 12:01 schrieb Roberto Ragusa:
Why can't sshd fork a new instance?
you have ask the sshd devs.
First guess: they do not use fork().
The whole premise of this thread comes from doing incorrect,
unsupported system upgrade on live system. Look, this method is even
described with red Warning frame:
https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-new-release/#_can_i_upgrade_between_fedora_linux_releases_using_only_dnf
There's no need to continue digressing wrt sshd behaviour.
Who cares about what is considered a "supported" upgrade method today?
The interesting topic on the table is the robustness (or lack of)
of the sshd daemon during an upgrade of its binaries and libraries.
That daemon is critical for remotely managed systems and the developers
usually take care of the implementation quality.
Never noticed that you can "systemctl restart sshd" without losing
existing ssh connections?
The answer to why is sshd failing to fork during ssl libs upgrade
is worth investigating.
It may lead to something to fix in the sshd code or in the way openssh
is patched/packaged.
(hasn't the xz backdoor thing given everybody a lesson on this?)
Regards.
--
Roberto Ragusa mail at robertoragusa.it
--
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
