* Markus Gaugusch wrote on Thu, Jun 27, 2002 at 11:48 +0200:
On Jun 27, Steffen Dettmer
wrote: Seems that it does not work for me. I upgraded as described, but didn't found a chrooted or setuid=sshd process after restarting sshd. How did you restart sshd? If you were logged in via ssh while restarting (rcsshd restart), it is not really restarted.
CooL. I knew the startproc isn't a nice thing... Even in -v it says nothing. Well, I tried rcssh, and I tried killall sshd /usr/sbin/sshd and even a /usr/sbin/sshd -f /etc/ssh/sshd_config to go for sure. I don't see any errors, only a sshd[24365]: Server listening on :: port 22.
Try killall sshd first and then start the new one (use a copy of sshd with different name and port while doing this).
Yes, this was my way. I even think, that rcsshd restart without having a copy with a different name on a different port is deadly since it seems it locks you out (and happily, after the stop, the rcsshd is killed by SIGHUP, and by that it doesn't start sshd). I verified with ps ax that no sshd process was running when I restarted it. I even did a "cmp" on sshd and the copy I made before upgrading, and both binaries differ. Any hints?? What did I wrong? And much more important: How do I make this stuff secure? oki, Steffen -- Dieses Schreiben wurde maschinell erstellt, es trägt daher weder Unterschrift noch Siegel.