On torsdagen den 17 juni 2010, you stated the following: > Hi, > > sh4 has the same problem. > > There was the following logs in syslog. > ---- > Jun 17 05:38:44 localhost lshd[26143]: lshd: Could not bind any address. > ----
The problem probably is that while lsh-server.postinst creates /etc/ssh/sshd_not_to_be_run, it doesn't actually stop sshd. I could fix that, as long as policy allows it, but the problem is that it is generally difficult to keep track of what ports and interfaces the local administrator has configured various services to use. Because two packages providing the same network service, such as HTTP/WWW, can be configured to use different ports, such packages generally do not declare conflicts with each other. Avoiding port conflicts is the responsibility of the administrator. This also means that a dependency on ssh-server is no guarantee that an SSH server is listening on port 22. Also, /etc/ssh/sshd_not_to_be_run is an old, ugly hack that should not be relied upon, and sshd could have already have been configured to listen to another port, meaning that is should not be disabled. In the case of SSH servers, it could be argued that there is little reason having more than one installed. On the other hand, I wouldn't want to remove one SSH server before I know that the next one works. At least not remotely, but on the third hand, configuring SSH servers is probably something you should do from a local console. Still though, I find it strange that lsh-server would be installed if openssh- server is already, since that would fulfil lam-runtime's ssh-server dependency. -- Magnus Holmgren holmg...@debian.org Debian Developer
signature.asc
Description: This is a digitally signed message part.
