How not to respond to a security advisory

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.

Expand all | Post comment

How not to respond to a security advisory 2006-01-19
Miles (3 replies)

Re: How not to respond to a security advisory 2006-01-19
Dwight

Re: How not to respond to a security advisory 2006-01-19
Anonymous

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

How not to respond to a security advisory 2006-01-19
Anonymous

I keep track of the OpenBSD mailing list. Unfortunately, this attitude is quite normal for Theo and it has spread to several of the other developers as well. If securelevels are so useless, why hasn't the OpenBSD team designed a better solution? I'm sure they'd give numerous reasons why. Until a better solution comes along, I'll stick to using securelevels, along with other tools, to help secure my *BSD systems.

[ reply ]

Link to this comment: http://www.securityfocus.com/comments/columns/380/32965#32965

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

How not to respond to a security advisory 2006-01-19
DS

How not to respond to a security advisory 2006-01-19
Anonymous (2 replies)

Re: How not to respond to a security advisory 2006-01-19
Kelly Martin

Re: How not to respond to a security advisory 2006-01-21
Anonymous

How not to respond to a security advisory 2006-01-19
Anonymous

Linux security contact 2006-01-19
Anonymous

Theo being theo... 2006-01-19
Anonymous (2 replies)

Re: Theo being theo... 2006-01-20
Anonymous

Re: Theo being theo...(Theo is best!) :) 2006-01-23
LinuxUser

What total nonsense. 2006-01-19
Anonymous