Test Priv3 w/ Recaptcha + DisQus

We need to test http://priv3.icsi.berkeley.edu/ to see if it is possible to amend its policy to allow recaptcha, DisQus, and other third parties other than the "big four".

added component::applications/tor bundles/installation owner::mikeperry parent::3546 priority::medium resolution::invalid status::closed type::task labels

Trac:
Parent: N/A to #3546 (moved)

Looks like there is an alternate implementation to test as well: http://sharemenot.cs.washington.edu/

I wonder how either of these deal with document.cookie...

Replying to mikeperry:

Looks like there is an alternate implementation to test as well: http://sharemenot.cs.washington.edu/

I wonder how either of these deal with document.cookie...

Sharemenot apparently does not work with our use case. It only works if 3rd party cookies are already enabled. It also does not deal with document.cookie.

Unknown if priv3 is the same on both counts or not.

Trac:
Keywords: MikePerryIteration20110814 deleted, MikePerryIteration20110828 added

Trac:
Priority: normal to major

Trac:
Keywords: MikePerryIteration20110828 deleted, MikePerryIteration20110911 added

I've come to believe these are just filtering approaches at heart.

I don't think they fit our model.

So 5 adversaries can't track you everywhere? Oh yeah, you totally have real privacy now. Because, you know, Google can't just pull that same data from DoubleClick (who they own), and Facebook can't just buy it from whoever...

This needs to work for arbitrary third parties, or it's not even worth publishing in academia, IMO.

Trac:
Keywords: MikePerryIteration20110911 deleted, N/A added
Points: 2 to N/A

Trac:
Priority: major to normal
Milestone: TorBrowserBundle 2.2.x-stable to N/A

Trac:
Resolution: N/A to invalid
Status: new to closed

closed

mentioned in issue #14057 (moved)

mentioned in issue tpo/applications/tor-browser#14057 (closed)