#15763: Need whitelist entry for www.fark.com and total.fark.com -------------------------------------+------------------------------------- Reporter: bit0mike | Owner: (none) Type: defect | Status: reopened Priority: Medium | Milestone: HTTPS-E next Chrome Component: HTTPS Everywhere/EFF- | release HTTPS Everywhere | Version: Severity: Blocker | Resolution: Keywords: | Actual Points: Parent ID: | Points: Reviewer: | Sponsor: -------------------------------------+------------------------------------- Changes (by bit0mike):
* status: closed => reopened * resolution: fixed => * severity: => Blocker Comment: Digging this 3 year old ticket back up to report that enough ad networks are on board with SSL that we finally were able to cut everything over at long last. One new exception: we still have cases where we iframe external plaintext sites, so the containing page must obviously also be plaintext, and so we’ve created a new go.fark.net hostname dedicated to that. That one is port 80 only, no 443 at all. Everything else under *.fark.com and *.fark.net EXCEPT for go.fark.net is now SSL, and sets an HSTS header to enforce it. go.fark.net will never support SSL, so that needs to stay blacklisted. So that should, uh, drastically simplify or eliminate the https://github.com/EFForg/https- everywhere/blob/master/src/chrome/content/rules/Fark.xml ruleset, yes? White -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/15763#comment:4> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs