I kind of see multi-licensing as having a different insurance policy for each fender on your car.
It's not like that at all. It's more like giving future developers an option to choose which license they want to use. Actually, that's exactly what it is. Wow, that was easy...
As mentioned previously on Slashdot, uselib() comes from Linux 0.13. It was kept for the a.out to ELF transition. Someone recently noticed it and said, "What is _that_ doing in my system?"
This is new code that's being looked at by hundreds of developers. It's pretty hard to get root kernel exploits when it's like that. Plus, this code doesn't introduce any calls with user level priviliges. (Read: no exploit)
You also can't convince me that the Linux kernel has far fewer holes found than the Windows kernel.
I don't believe it does either. If you really want a secure system, you wouldn't use Linux or Windows, but BSD. I consider Linux more secure than Windows because of its obscurity to viruses and spyware. Ironically enough, it is almost security by obscurity in reverse.
Microsoft relies on "responsible disclosure" to ensure that they are able to release fixes with vulnerability announcements.
Which rarely happens. I know if I found a Windows vulneribility the first place that would find out would be Bugtraq, and then maybe a week later I'd send it to Microsoft.
But even if I did give it to Microsoft, people have reported that they don't get back to them, they don't even know if anyone has seen the message. Doesn't sound very encouraging to those vuln. finders. And hey, we've already got a patch for that vuln, a Windows equivilant might have taken months.
Ah! So when kernel developers release a patch for a kernel exploit only a few hours after it hitting Bugtraq, it's because the kernel is only a few lines long? Of course, how silly of me.
With the security that is the hallmark of a Linux box
I hardly consider the security that Linux has worthy of the word "hallmark". It's better than Windows, sure, but it isn't secure (by default, especially) by any means.
Here's the mirrordot link: http://www.mirrordot.com/stories/8b06e35ecdf9d65de a75faf13d33d4e2/index.html
It's called being objective. You print two radical articles that oppose each other to give a guise of impartiality.
As mentioned previously on Slashdot, uselib() comes from Linux 0.13. It was kept for the a.out to ELF transition. Someone recently noticed it and said, "What is _that_ doing in my system?" This is new code that's being looked at by hundreds of developers. It's pretty hard to get root kernel exploits when it's like that. Plus, this code doesn't introduce any calls with user level priviliges. (Read: no exploit)
The difference between us and them is, well, at least they know how to spell strait jacket.