Linked by David Adams on Fri 11th Jul 2008 01:55 UTC, submitted by ohxten
Permalink for comment 322430
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
More News »
Sponsored Links



Member since:
2007-05-12
It's great that in the course of improving the OS itself, a bug elsewhere was found and fixed.
Given that the bug was in *yacc* (not in OpenBSD itself), it's not surprising that it remained for so long. This fix deserves credit in that even though the bug was outside OpenBSD, it was still fixed when found (not left for someone else to do).
Put it this way - Microsoft have been around for decades too, but despite their tens of billions of dollars (and thousands of programmers), they still haven't come up with an OS that is anywhere near as secure and robust as OpenBSD. Heck, they couldn't even come up with a firewall as good as *pf*
Edited 2008-07-11 03:57 UTC