Oops...
It turned out that my regular user (not root) started sshd with that
port number. and since only root allowed to open "high" ports, the
connection got terminated.
1. why did sshd / ubuntu allowed the regular user to even start the service,
when it's clear no connections will be received?
Thank you for reporting this bug. Have you checked if the port is in use
by another application?
** Changed in: openssh (Ubuntu)
Status: New => Incomplete
--
openssh-server is unable to receive connections on some ports
https://bugs.launchpad.net/bugs/251620
You received this bug notifica
running updated hardy, without any special hacks. and i only set one listening
port at a time:
- edit config file and changing the Port directive: "Port 22" / "Port 22184" /
etc.
- sudo /etc/init.d/ssh restart
- ssh localhost -p
--
openssh-server is unable to receive connections on some ports