I can't categorically state that it is the Openssh patch that's done this since I can't find anyone around to go and look at them to find out if they're sitting with an Ooops message or what's wrong with them. But it's suspicious enough that I've backed out 3.3p1 on the machines I can still get to and gone back to 2.9.9p2-98 for now.
I have removed all openssh packages from the ftp server to make sure that the packages don't break anything when installed. We will have better packages to offer on Monday.
And, yes, if I'd read the mailing list before I put the patches on then I probably wouldn't have bothered :-)
With issues like this, maybe Suse should pull these particular patches off the web page/ftp site? Especially since it appears that the 2.9.9p2 rpm's aren't vulnerable to the exploit that the advisory is meant to fix.
Trevor Hemsley, Security Specialist, Atos Origin Ltd, Whyteleafe, +44-(0)1883-628139
Thanks, Roman. -- - - | Roman Drahtmüller <draht@suse.de> // "You don't need eyes to see, | SuSE Linux AG - Security Phone: // you need vision!" | Nürnberg, Germany +49-911-740530 // Maxi Jazz, Faithless | - -