Public bug reported: NOTE: This bug is for trusty.
http://www.squid-cache.org/mail-archive/squid-users/201403/0065.html: > This bug caused the client_netmask directive in Squid-3.2 and Squid-3.3 releases to have no effect. The designed behaviour of masking client IPs in logs is now restored. Upstream issue tracker: http://bugs.squid-cache.org/show_bug.cgi?id=3769 In all versions of squid3 between 3.2 and 3.4.4 a pretty severe bug exists that disables the scrubbing of client IPs. Scrubbing of client IPs is extremely important for any privacy-aware and risk-aware provider. Based on the bzr commit fixing the bug (http://bazaar.launchpad.net/~squid/squid/3.4/revision/squ...@treenet.co.nz-20140212085229-edx2i4es622uo0gm) I made a patch. The diff of the bzr revision doesn't apply but the differences are solely due to cosmetic refactoring of method names in squid 3.4. I'm not familiar with the debian / ubuntu package maintenance tools so the patch ended up as a two-parter. ** Affects: squid3 (Ubuntu) Importance: Undecided Status: New ** Patch added: "First part of patch" https://bugs.launchpad.net/bugs/1561007/+attachment/4608645/+files/fix-3769.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1561007 Title: Upstream Bug #3769: client_netmask not evaluated since Comm redesign To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1561007/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
