Most of my debian installs took the recent ssh updates without a hiccup,
but two of them deposited the file /etc/ssh/sshd_not_to_be_run before
restarting and left no daemon listening.
I found this bit of code in /var/lib/dpkg/info/ssh.postinst
setup_startup() {
start=yes
[ -e /usr/share/debconf/confmodule ] && {
db_get ssh/run_sshd
start="$RET"
}
if [ "$start" != "true" ] ; then
/etc/init.d/ssh stop 2>&1 >/dev/null
touch /etc/ssh/sshd_not_to_be_run
else
rm -f /etc/ssh/sshd_not_to_be_run 2>/dev/null
fi
}
but I don't see the intent of the logic, or why one box would touch the
file but the other wouldn't? Ahaaaa, must have been in the initial debconf
for ssh. but when I do "dpkg --configure ssh" I get:
dpkg: error processing ssh (--configure):
package ssh is already installed and configured
Errors were encountered while processing:
ssh
Maybe "--force-things" would get around that, but I don't want to
regenerate my host keys.
How can I change this setting or control whether future updates create
the file?
// George
--
GEORGE GEORGALIS, System Admin/Architect cell: 646-331-2027 <IXOYE><
Security Services, Web, Mail, mailto:[EMAIL PROTECTED]
Multimedia, DB, DNS and Metrics. http://www.galis.org/george
