A bug in squid that was caused in the errorpage.c as explained on squid-cache.org has a patch available also there is currently a fully new version inclusive of this and other bugs but is not currently available on portage. Reproducible: Sometimes Steps to Reproduce: 1.Run squid with high traffic 2.Cause traffic with invalid headers that prompt errors 3. Actual Results: Assertion error's and the squid restarts Expected Results: Log errors and continue running 2004/07/13 19:22:20| assertion failed: errorpage.c:292: "mem->inmem_hi == 0" 2004/07/13 19:22:24| Starting Squid Cache version 2.5.STABLE5-CVS for i686-pc-l$
Not a devrel bug. Please be careful of whom you assign bugs to when you file them, so as not to waste our time and yours.
the link has been changed to Recruiters now. (if you made this bug with that link, shame on you, truly).
A link to the information would be nice chris
OK redirecting this bug... 2.5 Stable 6 will be going into portage shortly, so im using this bug as a tracker for the 2.5 stable 5 patches for people who dont want to use 2.5 stable 6 (or cant etc..) See list at http://www1.uk.squid-cache.org/squid/Versions/v2/2.5/bugs/
*** Bug 54332 has been marked as a duplicate of this bug. ***
cyfred: not sure this is a security issue... it's not classified as one in the patch page. Does squid stop running ? Or does it just restart ?
Its not a security issue.. who reassigned it? Its simply meant to be a tracker for me to make me put in some cosmetic patches... there are some major fixes in the list but the security one (ntml auth) is allready in portage...
reverting, sorry
Patches just gone into CVS for 2.4.7 2.5.5 2.5.6 Lets see what happens...
Closing this...
