On the other hand, despite the premise of open source that 'many eyes make all bugs shallow', the amount of code in the wild and the complexity of it (and the diversity of implementation languages) has pretty much guaranteed that there's more code than possible coverage.
No one has to come up with clever marketing for Microsoft exploits because everyone expects there to be tons of them, given the level of complexity, and that Microsoft will push patches for them, because it affects their bottom line. Meanwhile, it seems in the open source world, you need PR campaigns to goad the community into due diligence.
If people could casually look at code and see vulnerabilities, then we wouldn't have any.
Also: MS Shared Source initiative
Although your point about the methods of exploits changing the dynamic is valid.
>Also: MS Shared Source initiative
Fair point.
I think you're dismissing the level of experience, smarts, and inter-disciplinary knowledge it takes to find a bug like this. More than likely, even those with all those skills and at the 1% of them can't just eyeball code and go, "Ah yes, here." They're instead writing a lot of little tools and seeing what they can break. Then they go back, see what broke, and work out if its possible to exploit that exception or crash condition.
These types of tools and methods work just as well with closed source. Attacking closed source seems very unfair to me in these scenarios.
They could, but they don't. Same way I can look at the sky and see an asteroid. Possible? Sure. Likely? Not without some pretty advanced tools or a hell of a lot of luck.
Kind of a broad statement there, isn't it?
By your logic - Where do zero day Windows vulnerabilities come from then? People outside of Microsoft have certainly reported security issues to Microsoft in the past.
MS had it's fair share of security flaws in the past but give them credit for their current state. You sound like people still talking about BSODs, while it's certainly a thing in the past.
- https://technet.microsoft.com/en-us/library/security/dn63193...
I don't know where to get the multitude of security advisories for Unix systems listed all in one spot, but here are some links for popular distros:
- https://www.debian.org/security/
- https://access.redhat.com/security/updates/active/
- http://www.slackware.com/security/list.php?l=slackware-secur...
Anyone know where to go in order to get the Unix vulns all in one list?
Yes, certainly.