Microsoft's Security Development Process Under CC License
An anonymous reader writes "The H Online writes: 'Microsoft has placed its process for secure software development under a Creative Commons License. The company hopes that this will lead to more developers utilising its process for programming software more securely across the entire product lifecycle ...'"
Yes. It's what has contributed to very shitty quality. Of course the raw material, the managers and the engineers have to be mentioned as being incapable.
Beta is broken and the link to classic doesn't work. Stop wasting our time or there won't be anybody left here.
Pretty sure you have no idea about Unix internals vs NT internals. UNIX doesn't have ACL security.
Good luck interoperating with those, dipshit. And good luck getting them to work over NFS(*). And if you're not one of the 1% of environments out there using Kerberos for NFS, it's funny to me that you break the oldest rule of security - don't trust the client.
Give me root on one of your Linux machines and I'll copy any piece of NFS data I want unless you're one of the very few organizations using secured NFS.