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
Miles (3 replies)
Secure levels as a control is too coarse grained 2006-01-19
Anonymous (1 replies)
Re: Secure levels as a control is too coarse grained 2006-01-21
Anonymous
All true, but you're re-itterating points that the article agrees with.

The article isn't defending securelevels as useful or highly secure. It's simply saying they should either be fixed, or removed.

A crude, unqualified "won't fix because it is useless" is a bad position to take here. If it is not worth fixing due to lack of usefulness, it is worth removing the bad code that creates false security.


[ reply ]

Link to this comment: http://www.securityfocus.com/comments/columns/380/32988#32988
How not to respond to a security advisory 2006-01-19
Anonymous (1 replies)
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