#31230: Firefox addon blocked from agent by Google Safe Browsing service -------------------------------------+------------------------ Reporter: cypherpunks | Owner: (none) Type: defect | Status: new Priority: High | Milestone: Component: Circumvention/Snowflake | Version: Severity: Normal | Resolution: Keywords: | Actual Points: Parent ID: | Points: Reviewer: | Sponsor: -------------------------------------+------------------------
Comment (by dcf): I wonder if it's related to the zip bomb article I posted recently. That was on www.bamsoftware.com, not snowflake-broker.bamsoftware.com, but perhaps it carries across subdomains. I noticed about 2019-07-20 that Twitter started calling it an [https://twitter.com/safety/unsafe_link_warning?unsafe_link=https://www.bamsoftware.com/hacks/zipbomb/ "unsafe link"]. There's some kind of lookup service for Safe Browsing [https://support.google.com/webmasters/answer/3258249?hl=en&ref_topic=4596795 here], but it looks like it needs a Google account login. If it's the case that *.bamsoftware.com is blocked by Safe Browsing, we'll need a new top-level domain for the broker (and bridge). It's not that hard to do: we just need * a DNS record pointing to the broker's IP address * to restart the broker with the new domain name in `--acme-hostnames` * to update `brokerUrl` in config.js * push a new release of the WebExtension and update snowflake.torproject.org I don't think we need to push a new release of the client software, only the in-browser software. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/31230#comment:2> 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