As the title says, using most current TBB with Tor v0.2.2.32 Noscript is not configured to block web bugs under the "Advanced > Untrusted" tab. That seems unwise ...
Trac: Username: joyton
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items
0
Show closed items
No child items are currently assigned. Use child items to break down this issue into smaller parts.
Linked items
0
Link issues together to show that they're related.
Learn more.
By default we try to use NoScript in a minimal sense, because we don't believe in a filter-based approach to security. We never enabled this particular option because what the hell is a "Web Bug"? I imagine it is a 0x0 hidden pixel element. However, there could also be a broader definition that covers any number of items. For example, if everyone in the world blocked "Web bugs", those using them to undermine privacy would simply move to a new technique (such as empty CSS style sheets, or XMLHTTPRequest pings, or ???). Then, NoScript would have to block that. The leads to an escalating scenario where more and more web content types get blocked.
Sure, the "Block Web Bugs" checkbox probably doesn't damage much on the web now, but
clicking the checkbox commits us to the fallout of whatever arms race ensues for it that the NoScript guy has to fight.
Thanks Mike. That makes perfect sense. Sometimes us laypersons need people like the kinds Tor folks to explain these issues to us. I'm very pleased all of you are so kind.