#23947: Move Snowflake proxy page somewhere devs can write
-----------------------------------+------------------------------
 Reporter:  dcf                    |          Owner:  dcf
     Type:  project                |         Status:  needs_review
 Priority:  High                   |      Milestone:
Component:  Obfuscation/Snowflake  |        Version:
 Severity:  Normal                 |     Resolution:
 Keywords:                         |  Actual Points:
Parent ID:                         |         Points:
 Reviewer:                         |        Sponsor:
-----------------------------------+------------------------------
Changes (by dcf):

 * status:  assigned => needs_review


Comment:

 I copied the web files to https://snowflake.torproject.org/.
 {{{
 cake.coffeescript build
 rsync -rv build/ staticiforme:/srv/snowflake.torproject.org/htdocs/ && ssh
 staticiforme 'static-update-component snowflake.torproject.org'
 }}}
 Here is a small patch for review. attachment:bug23947.patch
 The first part changes references to !https://keroserene.net/snowflake/ to
 references to !https://snowflake.torproject.org/. The second part changes
 to the standalone broker (#22874). I changed to snowflake-reg-
 test.appspot.com, a domain front I had previously set up for the
 standalone broker, even though it doesn't work currently due to #25804.

 I tested this by loading a browser to https://snowflake.torproject.org/,
 removing the `-front` option from client/torrc to work around #25804, and
 running `tor -f torrc SOCKSPort auto`. The badge started animating and the
 bootstrap got to 100%.

 I also inspected the cookie set after opting in. The domain of the cookie
 was snowflake.torproject.org.

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

Reply via email to