Search: Home Bugtraq Vulnerabilities Mailing Lists Jobs Tools Beta Programs
The Promise and Peril of Palladium
Tim Mullen, 2003-03-17

Whether Microsoft's ambitious project is a security solution or a Trojan horse depends much on the company's intentions.

Comments Mode:
The Promise and Peril of Palladium 2003-03-17
Joseph Finley
The Promise and Peril of Palladium 2003-03-18
blacklight (1 replies)
Palladium, Longhorn, Memphis -- big secret code names 2003-03-22
Linux Torvald (2 replies)
Palladium, Longhorn, Memphis -- big secret code names 2003-03-26
Anonymous
Please. Keeping up with the ridiculous amounts of buffer overflows and trojanized shit in Linux such as sendmail, bind, apache, ssh, etc. is far more of a headache. If open source is so secure answer me why so many high profile software distributions like the above get hacked and replaced with trojans? Are these companies/groups not running "secure" Apache servers?

Interesting how you put down those who work with Microsoft products, like you are some higher being, yet you know every name of current Microsoft projects. Call me crazy, but if you dislike MS so much, why do you spend so much time researching their current products? FUD? Sounds like the US flying spy planes over N. Korea for exactly the same reason, fear of what may happen in the future (or what is happening).

I can't count how many revisions of one patch are released for all versions of *nix vulnerabilities like 5 days after the vulnerability becomes public. If MS released 4-5 revisions for every patch they released they wouldn't be in business right now.

Might want to rethink who is the Security Professional.

[ reply ]

Link to this comment: http://www.securityfocus.com/comments/columns/148/18806#18806
The Promise and Peril of Palladium 2003-03-23
Anonymous (1 replies)







 

Privacy Statement
Copyright 2009, SecurityFocus