> Yo Andrew! ... Right. > Then you update OpenSSL and it crashes all the ssh processes at the same > time. Been, there, done that. Thanks a lot.
After your suggestion that it couldn't be done, I tried it. While it took thinking, I could have done it had I not killall'ed my sshd's without changing the paths in my "restart-sshd" cron job to reflect the new location of sshd. :-/ Well, on the bright side, this will encourage me to make my script such that it restarts sshd from either location. (/usr/sbin, where Slackware puts it, or /usr/local/sbin, where the OpenSSH "make install" script puts it). Anyway, this would also be a solution. I have a shell script that checks for ssh to be running on a couple ports*. If it isn't running, the script starts it. I then placed this script into /etc/cron.hourly. So, if I had it scripted correctly, I could install a new version of libssl, install a new version of sshd, kill all running sshd's and then wait about an hour for my system to start them back up. *Actually, it runs nmap on, say, port 22. If there's no response, it considers sshd not to be running. Someone could fool it by running some other program on that port, but this is sufficient for me on a NAT'ed machine at home on a cable connection. _______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.netsys.com/full-disclosure-charter.html
