Contributed by jose on from the bugz-bugz-bugz- dept.
http://www.openbsd.org/errata.html "
(Comments are closed)
OpenBSD Journal
Contributed by jose on from the bugz-bugz-bugz- dept.
http://www.openbsd.org/errata.html "
(Comments are closed)
Copyright © - Daniel Hartmeier. All rights reserved. Articles and comments are copyright their respective authors, submission implies license to publish on this web site. Contents of the archive prior to as well as images and HTML templates were copied from the fabulous original deadly.org with Jose's and Jim's kind permission. This journal runs as CGI with httpd(8) on OpenBSD, the source code is BSD licensed. undeadly \Un*dead"ly\, a. Not subject to death; immortal. [Obs.]
By abot () lumor at chello dot se on mailto:lumor at chello dot se
Regards,
abot
Comments
By bumby () on
Sorry for usless comment ;)
By Tony () aschlemm@comcast.net on mailto:aschlemm@comcast.net
By Brad () brad at comstyle dot com on mailto:brad at comstyle dot com
Comments
By ABOT () lumor at chello dot se on mailto:lumor at chello dot se
.eod OK?
By Anonymous Coward () on
http://lists.netsys.com/pipermail/full-disclosure/2003-November/013338.html
OpenBSD will come up with any excuse to label a bug as not security-related. The whole separation of reliability/security is simply a marketing ploy so that OpenBSD has less "security advisories" than everyone else, being as everyone else considers DoS conditions and possibly exploitable bugs as security-related.
So many silly bugs...I thought you guys audited this for years? Whatever happened to "we had this fixed in OpenBSD 7 months ago?" (not that I've ever heard that before in real life). Seems to me as though you have lots of bugs that you created yourself. Humourous since most of your code is from NetBSD, and they don't have the problems. Were you blindfolded or something?
By Fred () hamvanger@inklaar.net on mailto:hamvanger@inklaar.net
It seems like 3.4's '004: RELIABILITY FIX: November 1, 2003' has been committed, even though it is not advertised on the 3.2 errata page. But then that patch was identical to the 3.3 patch, and I don't think that will be the case here.