[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #32536 [Applications/Tor Browser]: Security level set to "Safest" but JavaScript still Enabled.

To: undisclosed-recipients: ;
Subject: Re: [tor-bugs] #32536 [Applications/Tor Browser]: Security level set to "Safest" but JavaScript still Enabled.
From: "Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>
Date: Fri, 24 Jan 2020 06:52:39 -0000
Auto-submitted: auto-generated
Delivered-to: archiver@xxxxxxxx
Delivery-date: Fri, 24 Jan 2020 01:52:54 -0500
In-reply-to: <048.a8c22127d007b08f341f2242d094ffaf@torproject.org>
List-archive: <http://lists.torproject.org/pipermail/tor-bugs/>
List-help: <mailto:tor-bugs-request@lists.torproject.org?subject=help>
List-id: "auto: Tor bug tracker status mails" <tor-bugs.lists.torproject.org>
List-post: <mailto:tor-bugs@lists.torproject.org>
List-subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs>, <mailto:tor-bugs-request@lists.torproject.org?subject=subscribe>
List-unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-bugs>, <mailto:tor-bugs-request@lists.torproject.org?subject=unsubscribe>
References: <048.a8c22127d007b08f341f2242d094ffaf@torproject.org>
Reply-to: no-reply@xxxxxxxxxxxxxx, blackhole@xxxxxxxxxxxxxx
Sender: "tor-bugs" <tor-bugs-bounces@xxxxxxxxxxxxxxxxxxxx>

#32536: Security level set to "Safest" but JavaScript still Enabled.
--------------------------------------+--------------------------
 Reporter:  tor70001                  |          Owner:  tbb-team
     Type:  defect                    |         Status:  new
 Priority:  Medium                    |      Milestone:
Component:  Applications/Tor Browser  |        Version:
 Severity:  Normal                    |     Resolution:
 Keywords:  noscript                  |  Actual Points:
Parent ID:                            |         Points:
 Reviewer:                            |        Sponsor:
--------------------------------------+--------------------------

Comment (by cypherpunks):

 Huh, it also has a sex with CPU when a new tab is opened:
 {{{
 Error while fetching policy <unavailable> staticNS.js:56:21
 [NoScript] Policy was undefined, retrying in 1/2 sec... log.js:7:13
 Error while fetching policy <unavailable> staticNS.js:56:21
 [NoScript] Policy was undefined, retrying in 1/2 sec... log.js:7:13
 Error while fetching policy <unavailable> staticNS.js:56:21
 [NoScript] Policy was undefined, retrying in 1/2 sec... log.js:7:13
 Error while fetching policy <unavailable> staticNS.js:56:21
 [NoScript] Policy was undefined, retrying in 1/2 sec... log.js:7:13
 Error while fetching policy <unavailable> staticNS.js:56:21
 [NoScript] Policy was undefined, retrying in 1/2 sec... log.js:7:13
 Error while fetching policy <unavailable> staticNS.js:56:21
 [NoScript] Policy was undefined, retrying in 1/2 sec... log.js:7:13
 Error while fetching policy <unavailable> staticNS.js:56:21
 [NoScript] Policy was undefined, retrying in 1/2 sec... log.js:7:13
 Error while fetching policy <unavailable> staticNS.js:56:21
 [NoScript] Policy was undefined, retrying in 1/2 sec... log.js:7:13
 Error while fetching policy <unavailable> staticNS.js:56:21
 [NoScript] Policy was undefined, retrying in 1/2 sec... log.js:7:13
 Error while fetching policy <unavailable> staticNS.js:56:21
 [NoScript] Policy was undefined, retrying in 1/2 sec... log.js:7:13
 Error while fetching policy <unavailable> staticNS.js:56:21
 [NoScript] Policy was undefined, retrying in 1/2 sec... log.js:7:13
 Error while fetching policy <unavailable> staticNS.js:56:21
 [NoScript] Policy was undefined, retrying in 1/2 sec... log.js:7:13
 Error while fetching policy <unavailable> staticNS.js:56:21
 [NoScript] Policy was undefined, retrying in 1/2 sec... log.js:7:13
 Error while fetching policy <unavailable> staticNS.js:56:21
 [NoScript] Policy was undefined, retrying in 1/2 sec... log.js:7:13
 Error while fetching policy <unavailable> staticNS.js:56:21
 [NoScript] Policy was undefined, retrying in 1/2 sec... log.js:7:13
 Error while fetching policy <unavailable> staticNS.js:56:21
 [NoScript] Policy was undefined, retrying in 1/2 sec... log.js:7:13
 Error while fetching policy <unavailable> staticNS.js:56:21
 [NoScript] Policy was undefined, retrying in 1/2 sec... log.js:7:13
 Error while fetching policy <unavailable> staticNS.js:56:21
 [NoScript] Policy was undefined, retrying in 1/2 sec... log.js:7:13
 Error while fetching policy <unavailable> staticNS.js:56:21
 [NoScript] Policy was undefined, retrying in 1/2 sec... log.js:7:13
 Error while fetching policy <unavailable> staticNS.js:56:21
 [NoScript] Policy was undefined, retrying in 1/2 sec... log.js:7:13
 Error while fetching policy <unavailable> staticNS.js:56:21
 [NoScript] Policy was undefined, retrying in 1/2 sec... log.js:7:13
 Error while fetching policy <unavailable> staticNS.js:56:21
 [NoScript] Policy was undefined, retrying in 1/2 sec... log.js:7:13
 Error while fetching policy <unavailable> staticNS.js:56:21
 [NoScript] Policy was undefined, retrying in 1/2 sec... log.js:7:13
 Error while fetching policy <unavailable> staticNS.js:56:21
 [NoScript] Policy was undefined, retrying in 1/2 sec... log.js:7:13
 Error while fetching policy <unavailable> staticNS.js:56:21
 [NoScript] Policy was undefined, retrying in 1/2 sec... log.js:7:13
 Error while fetching policy <unavailable> staticNS.js:56:21
 [NoScript] Policy was undefined, retrying in 1/2 sec... log.js:7:13
 }}}

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/32536#comment:16>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online

_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Prev by Author: Re: [tor-bugs] #33018 [Core Tor/Tor]: Dir auths using an unsustainable 400+ mbit/s, need to diagnose and fix
Next by Author: Re: [tor-bugs] #5304 [Circumvention/Obfs4]: Obfsproxy should respect OutboundBindAddress in torrc
Previous by thread: Re: [tor-bugs] #32536 [Applications/Tor Browser]: Security level set to "Safest" but JavaScript still Enabled.
Next by thread: Re: [tor-bugs] #32536 [Applications/Tor Browser]: Security level set to "Safest" but JavaScript still Enabled.
Index(es):
- Author
- Thread