
What is becoming interesting is, how many of these are exploitable on XP?
For obvious reasons.
Flaws in Microsoft Word and Office Web Apps that allow hackers to execute malicious code on vulnerable systems have been fixed in Redmond's latest monthly batch of security bug fixes. In addition, two bugs at the kernel level of Windows XP and 7, and Server 2003 and 2008 R2, allow logged-in attackers to escalate their …
This post has been deleted by its author
This post has been deleted by its author
This post has been deleted by its author
Yeah, 310 packages sounds like CentOS 6.4 -> CentOS 6.5 to me. That is a sort of once or perhaps twice a year point update as AJ MacCleod says.
I'd usually expect the odd library and maybe a kernel update, oh, and Firefox if doing updates monthly.
CentOS 6 of course is Gnome 2.28 and will remain so for the rest of its life until around 2017/2020 (updates and then security only updates).
That would have been a joke, I would have thought that was clear.
The problem I seem to run into all the time as someone who is genuinely OS agnostic (I use pretty much all OSes, for whatever they're most appropriate for) if you say one is good at something, it's taken as some sort of slight against the others by their fans. If you make a joke about one OS, it somehow makes you a rabid fanboy for an other.
Sigh.
(That all said, I genuinely was updating a CentOS system that had those package numbers at the time.)
This post has been deleted by its author
As long as Google is throwing rocks they might as well pitch a few in their own house.
ISSO alert for Chrome with several vulnerabilities that can allow remote code execution as the logged in user was issued today.
I am giving Google credit for actually having a security team and testing all sorts of different software.
This post has been deleted by its author
"if the system has "Routing and Remote Access" switched on."
I always turn these off, always, as soon as the OS is installed. It's like keeping a light on for the burglars. These can be useful, but only for when they are needed, which is rare for me. Actually, I've never used either feature, except at work in an internal network. I feel sorry for those who don't know that they should have them turned off by default, which they aren't.
Microsoft default settings are set up with one thing in mind usually, reducing calls to their support line. They have gotten a little better security wise due to enterprise hammering on them but Microsoft's default OS choices have always left a bit to be desired. Here by default have an obscure dll for some long obsolete product included for compatibility reasons that also just happens to have a massive security vulnerability.