#24432: The meek<->moat tunneling isn't set up correctly ----------------------------------+-------------------------- Reporter: isis | Owner: isis Type: defect | Status: reopened Priority: High | Milestone: Component: Obfuscation/BridgeDB | Version: Severity: Normal | Resolution: Keywords: moat bridgedb-dist | Actual Points: Parent ID: #24689 | Points: 2 Reviewer: | Sponsor: SponsorM ----------------------------------+--------------------------
Comment (by isis): Replying to [comment:16 mcs]: > Replying to [comment:14 isis]: > > Google appears to want the passport of someone named "Tor Bridges" and the bank statement of the prepaid credit card that I gave, and I have neither of these things. Perhaps we can transfer the account ownership to TPO? Hopefully? Otherwise we'll need to make a whole new account and do #16650 all over again. > > I hope so. I guess the reflector is still running even though Google has suspended the Tor Bridges account? Strange terminology on their part. Yeah, it's very weird, the account itself is not suspended, I just can't pay for anything. Also, I can't access the cloud console to modify or look at the instance. > I also remember that we had to drop meek-google within Tor Browser as a PT due to some kind of service violation. If that is likely to happen again with the Moat reflector we should switch to Amazon or Azure now I suppose. Yeah, probably either Tor's lawyers should try to get a promise from Google that we're allowed to do this, or the sysadmin team should set up another reflector somewhere else using an account that TPO has financial control over? -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/24432#comment:17> 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