Slashdot Mirror
KDE 3.1 Delayed - For A Very Good Reason
woobieman29 writes "KDE.news reported on Saturday that the KDE 3.1 release that was scheduled for this week has been delayed until early January. This is happening due to some security concerns that have arisen during a security audit of the 3.1 CVS tree. Kudos to the KDE team for making sure that the product is fully baked before release.!"
Oh, and I forgot. First post.
Imagine the mess we'd be in if Microsoft could do this? Half of my gripes with M$ software stem from bugs and security holes. Now that they've become a monopoly by killing the competion, as opposed to outselling them via a offering a better product, they could take the time to squash bugs and plug holes. If all my practical reasons for disliking M$ go away, I'm left with nothing but dislike for their business practices...which are subjective decisions. That would certainly be a major blow to the anti-M$ crowd.
There are lies, damned lies, and statistics.
Obviously delaying the release until the security holes are fixed is the only course of action.
Since the betas and RC are now going to be exposed to the world for longer, are the security holes going to be disclosed so that we can take some action to secure our systems that are running these pre-release builds?
In other news, uppon reading this, Microsoft declared a company wide day of laughing, stating "...this is the most rediculus strategy we've ever seen! Why if we did this, we'd still be working on DOS 4 or 5." Later in the conversation, the spokesperson asked to take back that statement and said if we printed it the BSA would come after us for liscenses.
Gotta go, there is a knock on the door...
Comment forecast: Bits of genius surrounded by a sea of mediocrity.
You know... Microsoft gets a big bum rap for a lot of its security holes. I will admit they tend, like every other major software company out there to release programs that need a patch or two, but (aside from those dreaded buffer overflows, which they still can't seem to get around) most of the stuff that is considered a "security hole" by the fine *nix crowd is really what they claim it is; a feature.
You can blame market research for finding the desire for those "features", to be sure, but a lot of this stuff was put there because people wanted it there.
"Times have not become more violent. They have just become more televised."
-Marilyn Manson
MSIE doesn't render a page right: A perpetual bug that will never get fixed, probably doesn't render standards based code right due to some microsoft "proprietary" adaptation they call a "feature" and implemented intentionally to insure that since they have a monopoly web developers will code to match their "feature" and thus only MSIE will render the page right from there on. Linux gaping security hole: A MCSE who doesn't know how to properly configure a server and thinks he's hot for setting up a linux system. Or if it is an actual hole, something that will be usually be squashed within a couple hours of being discovered, most likely by the hacker who discovered it since he has a sense of community and is confident there are enough of the former to keep him in buisness for eternity.