Re: [tor-bugs] #25985 [Obfuscation/Snowflake]: Add AMP cache as another domain fronting option with Google

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#25985: Add AMP cache as another domain fronting option with Google
-----------------------------------+-----------------------------------
 Reporter:  twim                   |          Owner:  (none)
     Type:  project                |         Status:  needs_information
 Priority:  Medium                 |      Milestone:
Component:  Obfuscation/Snowflake  |        Version:
 Severity:  Normal                 |     Resolution:
 Keywords:                         |  Actual Points:
Parent ID:                         |         Points:
 Reviewer:                         |        Sponsor:
-----------------------------------+-----------------------------------

Comment (by twim):

 > twim, can you give a brief guide on what is needed to set up AMP?
 Sure. One needs to
 On the server side:
   Setup a web server accessible via domain name and preferably using TLS.
 This server has to wrap some *text* data inside the AMP markup. The text
 should be "visible" as AMP cache strips unnecessary content.
 On the client side:
   Assemble a special URL which contains:
     * correct AMP-styled host
     * random part (to go around caching)
     * the outgoing payload (as only GET requests can be made)
   Fetch the URL using some front and extract (and decode) data from the
 AMP page back.

 In a way it is pretty similar to meek except GET instead of POST and extra
 encoding/decoding thing.


 > I presume you at least need a Google account; is it something you set up
 in the Google Cloud Platform? Is there a fee?

 Curiously enough you don't need a Google account for that because the AMP
 project itself isn't solely a Google thing. It is just a special HTML
 markup that can be accelerated by any party incl. Google. You just set up
 an AMP version of your pages at your host and it just works. No GCP
 involved. There is no fee at the moment for page loading, there will only
 be on API calls (not our case). As IANAL, I am not aware whether this
 usage violates ToS. I couldn't find any.

 > I've seen different kinds of AMP URLs...
 > Do you know what the difference between all these URL styles is? Are
 they basically interchangeable? The first one looks like the best, if we
 can use it.


 I haven't managed to make URLs like
 https://www.google.com/amp/s/amp.reddit.com/blablabla to not redirect to
 the full article. I am probably just do not understand how this kind of
 links differs from others.

 > ​https://amp-reddit-com.cdn.ampproject.org/

 This is the kind of links I am using in amper. I guess that in theory
 *.cdn.ampproject.org can resolve to non-Google IPs as well. These hosts
 can be fronted by typical Google server names.

 > https://amp.reddit.com/

 This is the host from which one is serving their AMP pages.

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