, SecurityFocus 2005-11-29
When the SANS Institute, a computer-security training organization, released its Top-20 vulnerabilities last week, the rankings continued an annual ritual aimed at highlighting the worst flaws for network administrators. This year, the list had something different, however: The group flagged the collective vulnerabilities in Apple Computer's Mac OS X operating system as a major threat.
Expand all |
Post comment
Mac OS X security under scrutiny
2005-11-29
Anonymous (1 replies)
Anonymous (1 replies)
Mac OS X security under scrutiny
2005-11-29
Anonymous (1 replies)
Anonymous (1 replies)
Re: Mac OS X security under scrutiny
2005-11-29
Anonymous (1 replies)
Anonymous (1 replies)
Mac OS X security under scrutiny
2005-11-29
Anonymous (1 replies)
Anonymous (1 replies)
Mac OS X security under scrutiny
2005-11-29
Anonymous (3 replies)
Anonymous (3 replies)
Re: Mac OS X security under scrutiny
2005-11-30
Matthew Murphy (1 replies)
Matthew Murphy (1 replies)
Re: Re: Mac OS X security under scrutiny
2005-12-01
Anonymous (1 replies)
Anonymous (1 replies)
Mac OS X security under scrutiny
2005-11-29
Anonymous (1 replies)
Anonymous (1 replies)
Mac OS X security under scrutiny
2005-11-30
Jeffsters (1 replies)
Jeffsters (1 replies)

I keep that mac offline, play games, do photoediting etc. The internet right now is a dangerous place. We had all patches, internet security defs up to date, did not do dumb stuff, had recommended policies, strong passwords and it stopped nothing. It came according to it's payload log: ACTION-COMMAND LINE.
Guess I have about 1000 pages of these 'payload logs', files in javascript, c windows, the intel mac logs, their boot.efi; have several dvds from at least 3-4 pcs of c windows,registry.
Today in Linux got the hardware settings of my Hp. Very revealing, but just emailed it to myself, novell since that is the distro and to Hp security alert.
Consistent in the intel mac and xp is they complain of all devices 'not having the code for the architecture specified', bios and ram errors and the cpu ain't too happy about that malcode taking it's spot. Not sure which register the code is stealing, but perhaps the smart people will know what it means.
[ reply ]
Link to this comment: http://www.securityfocus.com/comments/articles/11359/34831#34831