You're joking, right? Open source supports the open standards when Exchange uses them.
For instance, you can use active directory as a regular LDAP instance (albiet with funny cn= syntax)
And you can access email boxes as IMAP folders.
In fact, most of the iCal processing is done by outlook and just stored in mail folder (accessible via IMAP). In fact, some people have actually gotten calendaring working with open source software via Exchange.
The only parts that aren't supported are those that aren't open. For instance, the MAPI messaging that exchange can do and those wonky objects in Active Directory that you can't access via the LDAP interface.
The next step in security will be nothing like that. I have to deal with security related issues on pretty much continual basis, and I will say that the next step isn't BNS, but rather, just actually implementing existing idea, best practices, and software.
The main problem with your next step is that it relies on Joe User becoming smarter. It also completely ignores a DDoS attack. Better passwords does not stop attacks from occuring.
Computers were built to do complex things in shorter times than humans. Recognizing and acting upon those attacks seems to be a natural evolution of something computers should be doing, not relying on Joe User to get smart.
The next step will be all about getting fundamentals into place. Firewalls, good strong user policies, filling in human weaknesses, basic IDS systems, astute administrators, and fundamentally secure software is the place where we should be aiming - not some pie in the sky Biological system.
The thought that everyone will accomplish these things seems less likely than a "Biological System" being implemented.
Slashdot Mirror
OSDL doesn't work on mono, btw. There's a full list of the projects they are currently working on at:
http://developer.osdl.org/
Majority of Open Source work is adding features to Open Source Software. I don't really see the elite ninja corps of industrial spies in that world.
You're joking, right? Open source supports the open standards when Exchange uses them.
For instance, you can use active directory as a regular LDAP instance (albiet with funny cn= syntax)
And you can access email boxes as IMAP folders.
In fact, most of the iCal processing is done by outlook and just stored in mail folder (accessible via IMAP). In fact, some people have actually gotten calendaring working with open source software via Exchange.
The only parts that aren't supported are those that aren't open. For instance, the MAPI messaging that exchange can do and those wonky objects in Active Directory that you can't access via the LDAP interface.
...
"OK. So why exactly is rewriting the kernel a problem?"
Because it's not needed. The kernel is being constantly rewritten via incremental (hopefully better) changes.
I would imagine that there is very little code in the kernel that has never been changed.
The main problem with your next step is that it relies on Joe User becoming smarter. It also completely ignores a DDoS attack. Better passwords does not stop attacks from occuring.
Computers were built to do complex things in shorter times than humans. Recognizing and acting upon those attacks seems to be a natural evolution of something computers should be doing, not relying on Joe User to get smart.
The thought that everyone will accomplish these things seems less likely than a "Biological System" being implemented.