Re: [tor-bugs] #29258 [Circumvention/Snowflake]: What is the IPv6 story with Snowflake

[Tor Bug Tracker & Wiki]

#29258: What is the IPv6 story with Snowflake
+--
 Reporter:  ahf |  Owner:  dcf
 Type:  task| Status:
|  needs_information
 Priority:  Medium  |  Milestone:
Component:  Circumvention/Snowflake |Version:
 Severity:  Normal  | Resolution:
 Keywords:  anti-censorship-roadmap-august  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
|  Sponsor28-must
+--

Comment (by dcf):

 Replying to [comment:8 dcf]:
 > My proposed solution is to migrate the broker to the Amsterdam data
 center.

 I've set up a new host in the Amsterdam data center and documented the
 installation instructions at
 [[org/teams/AntiCensorshipTeam/SnowflakeBrokerInstallationGuide]]. I
 copied over usernames, passwords, and ssh/authorized_keys, but not the
 contents of home directories or logs. You should be able to SSH and sudo
 as before.

 {{{
 IP: 37.218.245.111
 RSA:  2048 SHA256:dp0Xo/oN1qZfMuZnqgKEbeOsbU2qpDR60B5MLIRaAgg
 DSA:  1024 SHA256:DF5ofogjGur02gv8/ciU3wFA+YHNuAhUlel9Uv2KBlo
 ECDSA: 256 SHA256:6cskO6ch/kv2RbIMhTdwqpsd9vB8npzlZTlkWZJLoek
 }}}

 One problem: the IPv6 doesn't work :) I did the same thing I did last time
 with the bridge, but I cannot send nor receive IPv6 on the network
 interface. I'm going to contact support to see if I'm doing something
 wrong.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #29258 [Circumvention/Snowflake]: What is the IPv6 story with Snowflake

[Tor Bug Tracker & Wiki]

#29258: What is the IPv6 story with Snowflake
+--
 Reporter:  ahf |  Owner:  dcf
 Type:  task| Status:
|  needs_information
 Priority:  Medium  |  Milestone:
Component:  Circumvention/Snowflake |Version:
 Severity:  Normal  | Resolution:
 Keywords:  anti-censorship-roadmap-august  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
|  Sponsor28-must
+--

Comment (by arlolra):

 > My proposed solution is to migrate the broker to the Amsterdam data
 center.

 Maybe get some resolution on #31232 first

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #29258 [Circumvention/Snowflake]: What is the IPv6 story with Snowflake

[Tor Bug Tracker & Wiki]

#29258: What is the IPv6 story with Snowflake
+--
 Reporter:  ahf |  Owner:  dcf
 Type:  task| Status:
|  needs_information
 Priority:  Medium  |  Milestone:
Component:  Circumvention/Snowflake |Version:
 Severity:  Normal  | Resolution:
 Keywords:  anti-censorship-roadmap-august  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
|  Sponsor28-must
+--
Changes (by dcf):

 * status:  assigned => needs_information


Comment:

 Back in 2017, I inquired about IPv6 addresses. The reply is that IPv6 is
 only supported in one of the Greenhost data centers, namely Amsterdam

 > ...instances on our Amsterdam location we can give you an ipv6 prefix.
 Other locations don't have ipv6 available yet.

 The bridge is in the Amsterdam location, so I activated IPv6 for it back
 then. But the broker is in the Hong Kong location. I sent another support
 request this week to ask whether anything had changed, but IPv6 is still
 not available in Hong Kong.

 > Unfortunately there are no ipv6 block available yet for our Hong Kong
 customers.

 My proposed solution is to migrate the broker to the Amsterdam data
 center.
 1. Provision a new VM in Amsterdam.
 2. Set it up just as the current broker and rsync past logs to it.
 3. Change the snowflake-broker.bamsoftware.com DNS record to point to the
 new broker.
a. Restart our proxy-go instances. Web badge and WebExtension instances
 should restart automatically.
 4. Run the two brokers in parallel for a while.
 5. Shut down the Hong Kong broker.

 If all goes well, this plan means no required downtime. The downside I see
 is that during step 4, there will be two separate sets of logs
 (snowflake.log and metrics.log) being kept. We will need to either merge
 them, or ignore one copy during the transition.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #29258 [Circumvention/Snowflake]: What is the IPv6 story with Snowflake

[Tor Bug Tracker & Wiki]

#29258: What is the IPv6 story with Snowflake
+--
 Reporter:  ahf |  Owner:  dcf
 Type:  task| Status:  assigned
 Priority:  Medium  |  Milestone:
Component:  Circumvention/Snowflake |Version:
 Severity:  Normal  | Resolution:
 Keywords:  anti-censorship-roadmap-august  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
|  Sponsor28-must
+--
Changes (by gaba):

 * keywords:  anti-censorship-roadmap => anti-censorship-roadmap-august


Comment:

 thanks!

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #29258 [Circumvention/Snowflake]: What is the IPv6 story with Snowflake

[Tor Bug Tracker & Wiki]

#29258: What is the IPv6 story with Snowflake
-+
 Reporter:  ahf  |  Owner:  dcf
 Type:  task | Status:  assigned
 Priority:  Medium   |  Milestone:
Component:  Circumvention/Snowflake  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  anti-censorship-roadmap  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:  Sponsor28-must
-+
Changes (by dcf):

 * owner:  (none) => dcf
 * status:  new => assigned


Comment:

 > * Our broker currently has no IPv6 address.

 I'm claiming responsibility for getting an IPv6 address for the broker.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #29258 [Circumvention/Snowflake]: What is the IPv6 story with Snowflake

[Tor Bug Tracker & Wiki]

#29258: What is the IPv6 story with Snowflake
-+
 Reporter:  ahf  |  Owner:  (none)
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Circumvention/Snowflake  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  anti-censorship-roadmap  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:  Sponsor28-must
-+
Changes (by arlolra):

 * version:  Tor: unspecified =>
 * milestone:  Tor: unspecified =>


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #29258 [Circumvention/Snowflake]: What is the IPv6 story with Snowflake

[Tor Bug Tracker & Wiki]

#29258: What is the IPv6 story with Snowflake
---+---
 Reporter:  ahf|  Owner:  (none)
 Type:  task   | Status:  new
 Priority:  Medium |  Milestone:  Tor:
   |  unspecified
Component:  Circumvention/Snowflake|Version:  Tor:
   |  unspecified
 Severity:  Normal | Resolution:
 Keywords:  anti-censorship-roadmap-maybe  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:  Sponsor19
---+---
Changes (by phw):

 * keywords:   => anti-censorship-roadmap-maybe


Comment:

 A brief summary from [http://meetbot.debian.net/tor-meeting/2019/tor-
 meeting.2019-05-16-17.01.log.html an anti-censorship meeting] in which we
 discussed snowflake and IPv6:
 * Clients already can connect to snowflake proxies over IPv6.
 * Our broker currently has no IPv6 address.
 * We should have a way to ensure that an IPv6-only Tor Browser can use
 snowflake (see #29259).

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs