I'm not one to condone shitty attitudes.
However, I think in this case it's unfair to claim that one can have
no expectations of OpenBSD with regards to security patches. If I
could have no such expectations, I would not use OpenBSD in the first
place. I have these expectations based on a very impressive security
history for which the OpenBSD developers deserve much in the way of
praise.Additionally, loyal OpenBSD users may be interested in the details of
the vulnerability disclosure. There very well maybe loyal OpenBSD
users who wish to very politely inform ISC that there are large
numbers of BIND users who would appreciate the same level of
cooperation between ISC and OpenBSD as ISC affords others.On Wed, Jul 9, 2008 at 11:17 AM, Andreas Maus
wrote:
| Benjamin Herrenschmidt | Re: [PATCH] Remove process freezer from suspend to RAM pathway |
| Daniel Walker | Re: [Announce] [patch] Modular Scheduler Core and Completely Fair Scheduler [CFS] |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Andrew Morton | -mm merge plans for 2.6.23 |
git: | |
| David Miller | [GIT]: Networking |
| Hannes Eder | [PATCH 01/43] drivers/net/at1700.c: fix sparse warning: symbol shadows an earlier ... |
| Gerrit Renker | [PATCH 16/37] dccp: API to query the current TX/RX CCID |
| Herbert Xu | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
