Contributed by jose on from the missed-packets dept.
The problem described below only affects -current systems updated within a recent, narrow time frame. 3.4-stable, 3.4-release and earlier are NOT affected in any way.Note this affects a pretty small number of people because of the small window of vulnerability in this bug, but the nature of it is serious. Most of you wont have to worry, but if you've been keeping -current on your firewall in the past week or so, read the message and make sure you're patched.
Thanks, Daniel.
(Comments are closed)
By Anonymous Coward () on
Comments
By Anonymous Coward () on
By Daniel () Hartmeier on mailto:Hartmeier
By bsdguy () on
Comments
By Anonymous Coward () on
1.189 (fix) commited Sun Jan 25 18:47:15 2004 UTC
By Anonymous Coward () on
By Steve () on
/* $OpenBSD: pfctl_parser.c,v 1.188 2004/01/22 13:32:00 henning Exp $ */
I just installed a snapshot too, because I loathe building from source on this slow ass 75mhz sparcsation...
Comments
By Anonymous Coward () on
By pete gilman () on
if you keep -current *anything* on a production machine, you need to have your head examined.
Comments
By Anonymous Coward () on
had not a single problem with it for some years now. Read source-changes@ to know when big changes occur, test it on a development server, deploy it.
By Anonymous Coward () on
Believe or not I had an entire site running under -current. Shit happens even under -stable, its just a matter of taste.
Comments
By Kim () on
That guy couldn't login to his machine after upgrading to -current and Theo's response:
It is precisely for this reason that we ask users to use snapshots.
Big changes happen.
Comments
By tedu () on