gbishop / outfox

Automatically exported from code.google.com/p/outfox
Other
1 stars 0 forks source link

Support whitelisting #47

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Whitelisting can provide some level of user control over what sites can use
outfox services. Basically, when a site first requests access to an outfox
service, outfox will show a popup asking the user to allow, perm allow,
deny, or perm deny a host+domain access to that service. The user can later
change their mind and edit which sites are allowed/blocked via another UI.

This is extra hassle for the user, but something must be done to prevent
malicious sites from abusing outfox. It's not a huge problem for speech and
sound, just annoying if a site decides to yell at the user. It is a huge
problem for some hypothetical services like microphone recording or webcams
where data about the user can be shipped off to a remote site without the
user knowing about it.

Original issue reported on code.google.com by c...@unc.edu on 16 May 2009 at 2:49

GoogleCodeExporter commented 9 years ago

Original comment by c...@unc.edu on 16 May 2009 at 2:57

GoogleCodeExporter commented 9 years ago
trunk has message dialog asking permission when a page requests outfox. User 
can give
or deny permission just once or ask to save their choice for the (scheme, host, 
port)
site origin for future visits.

Options dialog under Addons -> Outfox lists all sites with saved allow/deny user
decisions. User can switch from allow to deny, deny to allow, or clear out the 
saved
choice so outfox prompts for access on the next visit.

Tested in Firefox 3.5 on OS X. Needs testing on win32 and linux. Needs testing 
in
Firefox 3.0 on all platforms.

Original comment by c...@unc.edu on 4 Jul 2009 at 7:20

GoogleCodeExporter commented 9 years ago

Original comment by c...@unc.edu on 7 Jul 2009 at 2:40