[tor-bugs] #23718 [Applications/Tor Browser]: Not able to log on to Protonmail with latest NoScript
    Tor Bug Tracker & Wiki 
    blackhole at torproject.org
       
    Sun Oct  1 19:34:32 UTC 2017
    
    
  
#23718: Not able to log on to Protonmail with latest NoScript
--------------------------------------+--------------------------
 Reporter:  cypherpunks               |          Owner:  tbb-team
     Type:  defect                    |         Status:  closed
 Priority:  High                      |      Milestone:
Component:  Applications/Tor Browser  |        Version:
 Severity:  Major                     |     Resolution:  fixed
 Keywords:  noscript                  |  Actual Points:
Parent ID:                            |         Points:
 Reviewer:                            |        Sponsor:
--------------------------------------+--------------------------
Changes (by gk):
 * status:  new => closed
 * resolution:   => fixed
Comment:
 Replying to [comment:23 cypherpunks]:
 > Okay, folks, gk is here. Moving to a new ticket...
 >
 > Replying to [comment:21 gk]:
 > > I don't have time debugging this now
 > Out of curiosity, what work are you busy with?
 > > but it seems we have a hint on what is going on (see comment:19).
 > Debugging on a weekend, while team doesn't have time.
 > > I guess our code blocking content scripts from accessing resources
 which is a severe fingerprinting vector is interfering with NoScript's
 code. That said: what's the impact of this issue?
 > Very high, critical.
 What I meant was whether the issue that is now #23723 is preventing
 NoScript from functioning properly or not. (It seems to me this bug is
 *not* preventing NoScript form behaving properly).
 > > I tested updating Noscript to 5.1.1 both in Tor Browser 7.0.6 and
 7.5a5 and while I saw the same error in the browser console I kept a
 working NoScript and the security slider was not messed up as comment:16
 reports (and other users, too, on IRC). Thus, we have at least one
 additional bug that is causing this or could that somehow be a result of
 Tor Browser breaking the entity resolution? If so, how can I reproduce
 this?
 > It is a new "feature" of a new "restartless update". Available since
 5.1.0.
 That could be it and would explain why I can't reproduce it by testing
 with clean 7.0.6 and 7.5a5 bundles.
 > > Oh, and I guess we should create a new bug for that and not clutter
 that one as the Protonmail issue should be resolved with 5.1.1.
 > Yeah, we have much more severe issues now.
 I created #23723 and #23724. Please move follow-up discussions to the
 respective bugs. This one got fixed with 5.1.1 it seems.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/23718#comment:25>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
    
    
More information about the tor-bugs
mailing list