To view parent comment, click here.
To read all comments associated with this story, please click here.
In the default installation? Very seldom. But fixing serious vulnerabilities in their packages (not default installation) ? Constantly. Just because a port isn't a part of the default installation, doesn't mean it's not meant to be fixed
And OpenBSD has so far fixed their holes within hours. It is typical for MOST FLOSS-projects. Security! Security! Security!
It is silly to choose compatibility over security. It is wiser to choose reduced functionality than it is to choose reduced security.
Who said anything about OpenBSD; proprietary vendors not only have to worry about their own products but products that rely on their own products; they have to ensure that in the process of fixing up a flaw, that in the same process they don't end up breaking compatibility with something that relies on it.
With that being said, however, I think the issue shouldn't necessarily be one of 'excusing' delays but instead asking why these companies haven't setup better communication with their partners so that rather than compromising on security fixes for the sake of compatibility, their partners are the first to know about the fix plus what has been fixed so that partners can issue updates for their respective tools at the same time updates are released for the main programme in question.
sappyvcv attacked a specific security policiy of open source projects, and this specific security policy happens to be the security policy of OpenBSD.
So open source projects sponsored by Novell, Redhat, IBM etc. don't have to worry about the projects depending on them?
And isn't this also true for open source projects? Or do you claim that no products are based on open source?







Member since:
2005-10-02
So basically you're saying OpenBSD is a quick hack?