On 1/10/2015 7:24 a.m., Sebastián Goicochea wrote: > Just happened to one of my squids 3.5.4, was this finally patched? Can't > find it in any of the release notes of newer versions. Its messy. There are several issues being reported in the bug 3279 bugzilla entry, simply because people hit the relatively harmless bug 3279 then they hit some other more fatal issue and sawy "bug 3279" in the log. Much like claiming that squid startup process was broken when there was a malicious request within the first few seconds of startup having completed. Just because "startup" was mentioned in the log *before* the failure. The patch that Yuri and HackXBack are talking about is the fix for bug 3482. Assertion falures saying "!isEmpty" in the log (usually seen 0-5 seconds after a bug 3279). It can be a side effect of bug 3279 having mucked up the state a little bit, but not always. That was patched and released months ago in 3.5.6. *Please* use the latest 3.5 releases. There have been _two_ major security vulnerability release since 3.5.4. And a great many bug fixes. Amos _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
