IEEE to Standardize OS Security Components
aster_ken writes "The Institute of Electrical and Electronic Engineers has started work on a standard for securing operating systems, as a recognition that software security is 'limited by the operating systems that underpin them', the organization said yesterday. The standard, dubbed IEEE P2200, will address external threats and intrinsic flaws arising from software design and engineering practices."
Did you Read The Fucking Post? It's littered with trash. Fucking idiot.
Graham
Linux - Fast Pane Relief
I used to work tech support for a large software company that develops OSes (who could that be?) and I learned customers are VERY concerned about security. They often asked questions like 'Should I be installing security updates? / Can someone get into my computer? / etc.' This same company had 1000 tech support calls queued the day MSBlaster hit. If one product is sporting a Certification sticker and another is not, the one sporting the sticker will have a bit more weight with the consumer.
This is even more true if they are one of the many thousands who had to call tech support to find out what the hell was wrong with their system.
This is typical of so many kiddies these days: "I want everything for free, even if it's something I will never need/use/understand".
Many products that are the result of the work of many people - like cars, toasters, and yes, even documents - cost money to produce. Learn to recognize which items are worth the amount on the price tag, and purchase accordingly.
I want to drag this out as long as possible. Bring me my protractor.
Hey, hey, hey, it's the big Master Control Program everyone's been talkin' about!
Won't that be grand? Computers and the programs will start thinking and the people will stop.
When you're on the other side of the screen, it all looks so easy.
End of line.
I can buy a linksys router with basic firewall functionality for $50. I can buy a NIC for $5. That's one helluva jump in price to get less functionality in a low profile case. So what if it says 3com on the box? My whole point is that this stuff doesn't need to be proprietary or expensive - it is only because there's no standard to commoditize the functionality.
That is a very good point, although my answer is the same: the best design approach is to separate applications into security-critical and non-security-critical parts, and minimize the size of the security-critical code. Luckily some people are already doing this.
Well, if you're a member of IEEE, you can usually get all that stuff for free. I'm a member (because as a student it only costs me like thirty bucks a year). I've pulled a bunch of documents from their archives and I've never payed a thing. Though, they do have an exagerated opinion of the value of dead trees. Some of the standards do require extra fees, I think, but none of the stuff I've used.
====
Crudely Drawn Games
Its "Institute of Electrical and Electronics Engineers." They changed it quite a while ago.