Univention Bugzilla – Bug 53163
The univention-ssh check should use the ucrv sshd/port instead of using port 22 in code
Last modified: 2022-10-19 14:51:19 CEST
In a customer environment the univention-ssh check fails because the port is not set to 22. [Errno None] Unable to connect to port 22 on 192.168.0.1 We should use the ucrv for the port and not use port 22 in code directly
hmm, I don't think we can use the UCR variable `sshd/port` because that specifies the ssh port of the local system and not the ssh port of all systems in the domain. Unfortunately the ssh port is also not part of the LDAP object of the computer. If we would change it then all other hosts in the domain would fail which use 22 as port. So we can't do anything here?!
could we perhaps have the self check uce `sshd/port`? as it stands it feels like univention is reccomending to leave the ssh port to a standard port, this is a security vulnerability if the univention server is exposed to the internet