Changes/Drop Sshd Socket

Dropping sshd.socket file

This is a rejected Change proposal for Fedora Linux.
This document represents a proposed Change that has been rejected or withdrawn as part of the Changes process. This page is preserved for historical record.

Summary

The sshd.socket behavior may cause the remote DoS and require a manual intervention to make server accepting the ssh connections back. sshd.service doesn't have these downsides

Owner

• Name: Dmitry Belyavskiy

• Email: dbelyavs@redhat.com

Current status

• Targeted release: Fedora Linux 40
• Last updated: 2023-12-16
• devel thread
• Fedora Discussion thread
• FESCo issue: #3098
• Tracker bug: <will be assigned by the Wrangler>
• Release notes tracker: <will be assigned by the Wrangler>

Detailed Description

A while ago, a dropping the sshd.socket from the openssh package was suggested in BZ#2025716 as there are several shortcomings with this approach that could lead to situations where users would loose access to a system while under DoS or memory pressure.

This change was implemented in rawhide & f39 and discussed on the devel list in a thread.

This change was reverted in f39 according to the FESCO decision.

Feedback

The change as implemented does not include a migration path for existing users of the sshd.socket unit to the sshd.service unit. We need some migration path, also suitable for OSTree

This means that systems updating from 38 to 39 and relying on sshd.socket for openssh access to the system will end up unreachable via SSH.

This is notably important for Fedora CoreOS where we will automatically update systems to the next Fedora version shortly after the release: https://github.com/coreos/fedora-coreos-tracker/issues/1558

We think this change needs to get more visibility and should go through the change process and be evaluated for inclusion in Fedora 40.

See also the mentioned before thread.

Benefit to Fedora

This change will prevent remote DoS in the case the sshd.socket is acivated.

Scope

• Proposal owners: the migration scriptlet is the best solution.

• Other developers: check the dependencies on sshd.socket

• Release engineering: #Releng issue number

• Policies and guidelines: N/A (not needed for this Change)

• Trademark approval: N/A (not needed for this Change)

• Alignment with Community Initiatives: N/A

Upgrade/compatibility impact

The worst case the remote access to the system will be lost of sshd.socket is enabled and the system is not switched to using sshd.service before upgrade

How To Test

1. Enable sshd.socket
2. Upgrade
3. Check remote access over sshd

User Experience

See "Benefit for Fedora"

Contingency Plan

Reverting the change

• Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
• Contingency deadline: N/A (not a System Wide Change)
• Blocks release? N/A (not a System Wide Change), Yes/No

Documentation

N/A (not a System Wide Change)

Release Notes

The change should be mentioned in the Release Notes.