The flaw affects KDE 3.2.0 up to and including KDE 3.5.0, it said.The newest version of KDE released in November, KDE 3.5, is apparently not affected. Does this make any sense?
1 posted on
01/23/2006 8:21:57 AM PST by
ShadowAce
To: rdb3; chance33_98; Calvinist_Dark_Lord; Bush2000; PenguinWry; GodGunsandGuts; CyberCowboy777; ...
2 posted on
01/23/2006 8:22:14 AM PST by
ShadowAce
(Linux -- The Ultimate Windows Service Pack)
To: ShadowAce
To: ShadowAce
I thought only IE had these kind of issues..... ;)
To: ShadowAce
WINDOWMAKER!!
It Works!
Very low resource overhead too . . . And it looks neat!
8 posted on
01/23/2006 8:58:15 AM PST by
blues_guitarist
(Ez. 38 & 39 <--- It's closer than you think!)
To: ShadowAce
The flaw affects KDE 3.2.0 up to and including KDE 3.5.0, it said. The newest version of KDE released in November, KDE 3.5, is apparently not affected. Does this make any sense? Only if the current version of KDE 3.5 is at revision level 1 or higher (3.5.1 or higher). It would have been smarter writing to have been more specific, rather than just referring to the major/minor release numbers.
10 posted on
01/23/2006 9:06:53 AM PST by
kevkrom
To: ShadowAce
The KDE hole was discovered Thursday... After being in place since at least February 2004, when KDE 3.2 was released. Someone want to explain that "many eyeballs" business to me again?
FreeRepublic.com is powered by software copyright 2000-2008 John Robinson
