[Bug 2069041] Re: Changing Port in sshd_config and restarting ssh.service without effect
Nick Rosbrook
2069041 at bugs.launchpad.net
Thu Jun 13 15:27:45 UTC 2024
There is really no way around requiring a daemon-reload. The best thing
we can do here is improve the documentation to make this clear to users.
** Changed in: openssh (Ubuntu Noble)
Status: New => Triaged
** Changed in: openssh (Ubuntu Noble)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
** Changed in: openssh (Ubuntu)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
** Changed in: openssh (Ubuntu)
Importance: Undecided => Medium
** Changed in: openssh (Ubuntu Noble)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2069041
Title:
Changing Port in sshd_config and restarting ssh.service without effect
Status in openssh package in Ubuntu:
Triaged
Status in openssh source package in Noble:
Triaged
Bug description:
Changing the Port directive in sshd_config and restarting ssh.service
is without effect, sshd keeps listening to port 22.
Also mentioned in https://discourse.ubuntu.com/t/sshd-now-uses-socket-
based-activation-ubuntu-22-10-and-later/30189/32
Steps to reproduce:
1. Install Ubuntu 24.04 LTS
2. Change Port directive in /etc/ssh/sshd_config to Port 2233
3. Restart ssh.service
4. Observe sshd still listening to port 22
Expected behaviour: sshd changes port to 2233
Actual behaviour: sshd keeps listening to port 22
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2069041/+subscriptions
More information about the foundations-bugs
mailing list