Opened 13 years ago

#667 closed defect (Fixed)

Error loading pages w/FF3b5

Reported by: defcon Owned by:
Priority: Very High Milestone:
Component: Applications/Torbutton Version: 1.1
Severity: Keywords:
Cc: defcon, sabato Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


Exception in sandbox evaluation. Date hooks not applied:
[Exception... "Not enough arguments" nsresult: "0x80570001 (NS_ERROR_XPC_NOT_ENOUGH_ARGS)" location: "JS frame :: chrome://torbutton/content/torbutton.js :: anonymous :: line 1722" data: no]

[Automatically added by flyspray2trac: Operating System: All]

Child Tickets

Change History (6)

comment:1 Changed 13 years ago by defcon

unchecking javascript hooking fixes the issue

comment:2 Changed 12 years ago by keb

i got same error going to the home (i.e. no javascript on the page)
with torbutton turned on.
torbutton: 1.1.18alpha
firefox: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b5) Gecko/2008041514 Firefox/3.0b5
os: xubuntu 8.04

comment:3 Changed 12 years ago by sabato

I'm experiencing the same issue on ubuntu 8.04 + Firefox/3.0b5
torbutton: 1.1.18alpha

comment:4 Changed 12 years ago by flytoggle

that's because the javascript is inserted into the page by torbutton as a security feature - "# Hook Dangerous Javascript (crucial):
This setting enables the Javascript hooking code. Javascript is injected into pages to hook the Date object to mask your timezone, and to hook the navigator object to mask OS and user agent properties not handled by the standard Firefox user agent override settings. " -- from the torbutton homepage

comment:5 Changed 12 years ago by mikeperry

Yes, that is correct. This issue is tied to the Hook Dangerous Javascript pref. Disabling it will
cause your timezone and some useragent info to potentially leak though. Setting he TZ environment
variable to UTC can counteract the timezone leak as a workaround. I have filed a bug against
firefox to fix the functionality torbutton relies on to do these hooks:

comment:6 Changed 12 years ago by mikeperry

flyspray2trac: bug closed.
Fixed in 1.2.0rc1.

Note: See TracTickets for help on using tickets.