On Jun 25, Martin Wilck
Being able to install the new version in parallel to the old one and only disable the old one when the new one proves to work would be a nice option. I copied the old one to sshd-x and started it on a different port (sshd-x -p 1022). After that you can experiment with the new version (killall sshd ;). You can't restart the sshd-x after update, because it may fail with the new config file, so be careful or pass it another config file as option. My personal (first try) was to start a vnc server and access it through a box beneath mine. Quite ressource hungry, but works even with totally f*cked up ssh. As far as I can tell, you are safe without md5 passwords enabled (updated a 7.3 box successfully). I'm sure, that suse people are heavily struggling around with the md5 problem and expect a fix soon ...
Markus PS: debian works with md5 and 3.3p1, so a linux fix for the pam problem is at least available (but maybe debian people fixed themselves, and it wasn't with the official 3.3p1) -- __________________ /"\ Markus Gaugusch \ / ASCII Ribbon Campaign markus@gaugusch.at X Against HTML Mail / \