This case is quite illustrative, but not the only one. There are so many different cases with a single root of the problem - programmer's concern. what the key difference between Unix and Windows kernels and API's? Not in usability - some one-step actions in Windows you'll need to implement making 3-5 Unix calls. Not in marketing position - it's a good question which system is more popular in mission-critical applications. And not in code policy - OpenSource or closed one... It's in action permissions - Windows will swallow buggy and instable code, but Unix will kick it off permanently. Without ANY questions. Such an issues will grow until the security concern won't become first and primary concern in kernel archicture of Windows OS. That's it.

[ reply ]

Link to this comment: http://www.securityfocus.com/comments/columns/364/32595#32595