IWETHEY v. 0.3.0 | TODO
1,095 registered users | 0 active users | 0 LpH | Statistics
Login | Create New User
IWETHEY Banner

Welcome to IWETHEY!

New Then I suggest...
...that you simply not upgrade any of your systems that might be affected. Wait until someone can figure out how to exploit it. And then you can attempt to maybe possibly use your machine as an after-the-fact honeypot.

Meanwhile, I'll just go run red-carpet, update my system, and not worry about it.
-YendorMike

Real programmers use "vi a.out".
New I've run into double-free problems before
The memory arena is corrupted, and eventually the program core dumps. I can't get my mind around a way to reliably exploit it. Getting the condition to happen and somehow using it for a denial of service attack, I can see how that might be possible, but it's not worth worrying about for a home system.
Where each demon is slain, more hate is raised, yet hate unchecked also multiplies. - L. E. Modesitt
     zlib advisory - (ben_tilly) - (16)
         Re: zlib advisory - a similar link. - (a6l6e6x)
         Remedy? - (kmself) - (3)
             Erg. - (static)
             Well OpenBSD was never vulnerable. :-) - (ben_tilly) - (1)
                 OpenBSD as server - (kmself)
         Re: zlib advisory - (pwhysall) - (1)
             Re: zlib and up2date - (a6l6e6x)
         Microsoft vulnerable too - uses zlib code - (admin) - (2)
             Risk: adopting FS code without adopting FS practices - (kmself) - (1)
                 But note that MS doesn't update the build #'s - (tonytib)
         I'm confused about the entire thing - (wharris2) - (5)
             DoS is an attack - (ben_tilly) - (4)
                 Re: DoS is an attack - (wharris2) - (3)
                     Then I suggest... - (Yendor) - (1)
                         I've run into double-free problems before - (wharris2)
                     It's a known class of exploit... - (kmself)

Colossal liquid insect.
37 ms