Search: Home Bugtraq Vulnerabilities Mailing Lists Jobs Tools Vista
AtStake fires executive over Microsoft criticism
Ted Bridis, The Associated Press 2003-09-25

The chief technology officer for a technology firm that works closely with Microsoft Corp. lost his job after he helped write a study critical of the insecurity of Microsoft software.

Comments Mode:
Keep your mouth shut! 2003-09-25
The420Zodiac (2 replies)
Keep your mouth shut! 2003-09-25
Anonymous (1 replies)
Keep your mouth shut! 2003-09-26
Anonymous
Keep your mouth shut! 2003-09-26
Anonymous
Wrongful Termination 2003-09-26
Anonymous
AtStake... sellouts 2003-09-26
Anonymous (1 replies)
AtStake... sellouts 2003-09-26
Anonymous
where's the study? 2003-09-26
Anonymous (1 replies)
where's the study? 2003-09-27
Anonymous
Link to the CCIA report. 2003-09-26
Anonymous (1 replies)
Link to the CCIA report. 2003-09-29
Disinterested Observer
Nothing new for @Stake 2003-09-26
Anonymous (2 replies)
Nothing new for @Stake 2003-09-26
Anonymous
Nothing new for @Stake 2003-09-27
Anonymous (1 replies)
l0pht != atstake...wrong 2003-09-29
Anonymous
AtStake made the right choice 2003-09-27
Anonymous
AtStake was right 2003-09-28
Anonymous
Look, I agree in principle with the report finding that 90% market share leads to huge security risk. Seems like kind of a no-brainer. Even if msoft was doing a better job (or any job) at securing their products, it would still be a no-brainer.

However, if you are going to publish a critical paper, and even more importantly, use your damn business title in the press conference, you better run it by your employer first. Now if he did that and they said run with it, then obviously AtStake is at fault.

If you want a position where you can publish this kind of report and not get fired, get a phd and get tenure at a university. That's the purpose of tenure, to protect academic freedom. Either that or run your own company. There is no such thing as tenure when you work for someone else.

[ reply ]

Link to this comment: http://www.securityfocus.com/comments/articles/7069/22639#22639







 

Privacy Statement
Copyright 2008, SecurityFocus