#46, Hal knock off the spin - you know dern well what I mean - "where people would have gone after W2K systems, they are now turning their attention to the Linuces and wrecking havoc on older and unpatched OpenSSH daemons running on most Linuces." "Further, you tell me the percentage of Linuces admins that have one percent of one clue about privsep, or how to manually set it in the CLI - post that list!"
This called into question for me that OpenSSH, and SSH period, may not be nearly as secure
as we might have thought. Also, I am speaking to client systems we are called on to repair, or restore, or migrate [away from Linuces to W2K3, ironically]. In most cases, we see OpenSSH implementations which pre-date 3.7.2 - which as you should know, do not support privsep...
From your last post, it is very clear to me that you are not at all interested in any meaningful discourse and that aside from clipping links into threads, you likely are not doing a great deal.
The bottom line is, that if a Linuces or any Nix is running SSH and it isn't controlled, someone is going to root that system. There are indeed a great many issues now emerging indicating just how loose OSS is - I mean if SSH is not secure, or can be exploited [because it is open], then what OSS ever could be? It's over as far as I am concerned. That was the last straw for us. OSS and any hint of it being secure just does not seem possible.
And finally, yeah - we had the client's systems patched and restored in a few hours. We're now moving them off of OSS and onto either a commercial Unices, or W2K3. I know which they can afford and it isn't a Unices.
|