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

Re: [tor-bugs] #5042 [HTTPS Everywhere: Chrome]: Chrome port appears to not respect exclusions in rulesets (was: Reload loop when editing a LinkedIn profile (Chrome only))

#5042: Chrome port appears to not respect exclusions in rulesets
--------------------------------------+-------------------------------------
 Reporter:  pde                       |          Owner:  aaronsw 
     Type:  defect                    |         Status:  assigned
 Priority:  critical                  |      Milestone:          
Component:  HTTPS Everywhere: Chrome  |        Version:          
 Keywords:                            |         Parent:          
   Points:                            |   Actualpoints:          
--------------------------------------+-------------------------------------
Changes (by pde):

  * priority:  major => critical


Comment:

 https://gitweb.torproject.org/https-
 everywhere.git/commitdiff/f6d18455d076aff69043e50fabe8992baad06180 fixed
 the problem in the LinkedIn Ruleset (which looks like a JavaScript
 redirection loop to me); however, it doesn't fix it in Chrome.

 That turns out to be because of a much more serious problem, which is that
 the Chrome port implementation of <exclusion pattern="regexp"> elements in
 the rulesets!

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/5042#comment:6>
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