This bug was fixed in the package openssh - 1:9.3p1-1ubuntu1
---
openssh (1:9.3p1-1ubuntu1) mantic; urgency=medium
* Merge with Debian unstable (LP: #2025664). Remaining changes:
- debian/rules: modify dh_installsystemd invocations for
socket-activated sshd
- debian/op
I adjusted our documentation for the next Debian upload (which will get
merged into Ubuntu at some point and will close this bug then):
https://salsa.debian.org/ssh-
team/openssh/-/commit/a183f4934873b0dd663177e1772090d1d7a6a631
** Changed in: openssh (Ubuntu)
Status: Incomplete => Fix C
As I noted above, the key was restarting ssh.socket, not ssh. Even
though systemctl status ssh.socket reported (claimed) that the service
was listening on both 22 and 7022, this didn't come into effect until I
restarted ssh.socket. This last step was essential to getting this to
work. Restarting ss
According to your output from `systemctl status ssh.socket`, it is
listening on both ports. But, to be sure, I tried this in a fresh 23.04
container:
root@lunar:~# systemctl edit ssh.socket # This opens a text editor to create
/etc/systemd/system/ssh.socket.d/override.conf
root@lunar:~# cat /etc
Ok. The solution to this problem was to restart not ssh.service but ssh.socket.
Thus:
sudo systemctl daemon-reload
sudo systemctl restart ssh.socket
I think the documentation, such as it is, should make this clear.
Googling around gets you several hits that say you should sudo systemctl
restart s
Thank you for the prompt reply. If my configuration is correct, why is
it that I cannot connect on port 7022? I don't see a listener for it, so
I suspect my configuration in
/etc/systemd/system/ssh.socket.d/listen.conf is either not being read or
is being supplanted by the configuration in
/lib/sys
It is expected that you have both ssh.socket and ssh.service on your
system. The ssh.socket unit is enabled by default and is responsible for
listening on the configured port. Once it receives a connection it
activates ssh.service (which is what actually spawns sshd).
As the comment in /etc/ssh/ss
This is probably not a bug related to ssh but to the configuration
changes introduced by Ubuntu.
** Package changed: ubuntu => openssh (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.l
8 matches
Mail list logo
