Search: Home Bugtraq Vulnerabilities Mailing Lists Jobs Tools Vista
How not to respond to a security advisory
Jason Miller, 2006-01-18

A recently announced weakness in the BSD securelevel system isn't going to be fixed in OpenBSD. While securelevel may have problems, the vendor's security response is unacceptable and doesn't fit with their stated goals.

Comments Mode:
How not to respond to a security advisory 2006-01-19
Anonymous (1 replies)
Re: How not to respond to a security advisory 2006-01-25
Matthew Murphy
Why does Jason need to include "formal input from the OpenBSD team"? He has it, in the form of the comment from Theo De Raadt.

OpenBSD didn't choose to "let it die on the vine" (it still ships, vulnerability-and-all). They just aren't fixing it because it's one less security bug for them to admit to.

Your post is typical of the attitude of Theo and a few other OpenBSD devs -- an attitude that ultimately renders the project's stated goal of a more secure system more difficult to achieve.

[ reply ]

Link to this comment: http://www.securityfocus.com/comments/columns/380/33026#33026
Linux security contact 2006-01-19
Anonymous
Theo being theo... 2006-01-19
Anonymous (2 replies)
Re: Theo being theo... 2006-01-20
Anonymous
What total nonsense. 2006-01-19
Anonymous
"Root problem" again 2006-01-24
Alexey Vesnin
How not to respond to a security advisory 2006-01-25
Michael Favinsky (1 replies)
this is a non-issue 2006-02-04
Anonymous







 

Privacy Statement
Copyright 2008, SecurityFocus