[Bug 1561007] [NEW] Upstream Bug #3769: client_netmask not evaluated since Comm redesign
Launchpad Bug Tracker
1561007 at bugs.launchpad.net
Wed Mar 23 15:04:33 UTC 2016
You have been subscribed to a public bug by Robie Basak (racb):
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/squid3@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: squid
Importance: Unknown
Status: Unknown
** Affects: squid3 (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: squid3 (Ubuntu Trusty)
Importance: Undecided
Status: New
--
Upstream Bug #3769: client_netmask not evaluated since Comm redesign
https://bugs.launchpad.net/bugs/1561007
You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report.
More information about the Ubuntu-server-bugs
mailing list