Re: [tor-bugs] #29480 [Circumvention/BridgeDB]: Expose bridge pool assignments again

[Tor Bug Tracker & Wiki]

#29480: Expose bridge pool assignments again
+
 Reporter:  irl |  Owner:  phw
 Type:  defect  | Status:  closed
 Priority:  Medium  |  Milestone:
Component:  Circumvention/BridgeDB  |Version:
 Severity:  Normal  | Resolution:  fixed
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+
Changes (by karsten):

 * status:  needs_information => closed
 * resolution:   => fixed


Comment:

 Bridge pool assignments are back! Closing.

--
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] #29480 [Circumvention/BridgeDB]: Expose bridge pool assignments again

[Tor Bug Tracker & Wiki]

#29480: Expose bridge pool assignments again
+---
 Reporter:  irl |  Owner:  phw
 Type:  defect  | Status:  needs_information
 Priority:  Medium  |  Milestone:
Component:  Circumvention/BridgeDB  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+---

Comment (by karsten):

 Alright, the rsync is working, now I need to look into resurrecting the
 CollecTor module. Created #31558 for that part.

--
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] #29480 [Circumvention/BridgeDB]: Expose bridge pool assignments again

[Tor Bug Tracker & Wiki]

#29480: Expose bridge pool assignments again
+---
 Reporter:  irl |  Owner:  phw
 Type:  defect  | Status:  needs_information
 Priority:  Medium  |  Milestone:
Component:  Circumvention/BridgeDB  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+---

Comment (by karsten):

 I just created #31515 for the sysadmin side of this.

--
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] #29480 [Circumvention/BridgeDB]: Expose bridge pool assignments again

[Tor Bug Tracker & Wiki]

#29480: Expose bridge pool assignments again
+---
 Reporter:  irl |  Owner:  phw
 Type:  defect  | Status:  needs_information
 Priority:  Medium  |  Milestone:
Component:  Circumvention/BridgeDB  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+---

Comment (by phw):

 I just noticed an error message in the logs:
 {{{
 1566241638:descriptors:<36>Aug 19 19:07:18 collector-ssh-wrap[23644]: The
 SSH_ORIGINAL_COMMAND ('rsync --server -logDtpre.iLsfxC .
 /srv/collector.torproject.org/collector/in/bridge-pool-
 assignments/polyanthum/') is not on the whitelist
 }}}
 This seems like an issue on colchicifolium's side. Do we need an update in
 its SSH configuration?

--
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] #29480 [Circumvention/BridgeDB]: Expose bridge pool assignments again

[Tor Bug Tracker & Wiki]

#29480: Expose bridge pool assignments again
+---
 Reporter:  irl |  Owner:  phw
 Type:  defect  | Status:  needs_information
 Priority:  Medium  |  Milestone:
Component:  Circumvention/BridgeDB  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+---

Comment (by phw):

 Replying to [comment:8 karsten]:
 > We can include bridge pool assignments in CollecTor again. Yes, please
 set up an rsync to copy files to colchicifolium to a directory
 `/srv/collector.torproject.org/collector/in/bridge-pool-
 assignments/polyanthum/`. I'll take care of the CollecTor side of things
 then which includes reverting an earlier commit and refreshing that enough
 to run again. Thanks!
 [[br]]
 I [https://gitweb.torproject.org/project/bridges/bridgedb-
 admin.git/commit/?id=fc7881b70826147356fcabd9d191dbcefb42 just
 updated] our script sync-to-colchicifolium to make this happen. You should
 see assignments.log files in this directory in less than two hours. Please
 let me know if that's not the case, or if anything else went 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] #29480 [Circumvention/BridgeDB]: Expose bridge pool assignments again

[Tor Bug Tracker & Wiki]

#29480: Expose bridge pool assignments again
+---
 Reporter:  irl |  Owner:  phw
 Type:  defect  | Status:  needs_information
 Priority:  Medium  |  Milestone:
Component:  Circumvention/BridgeDB  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+---

Comment (by karsten):

 We can include bridge pool assignments in CollecTor again. Yes, please set
 up an rsync to copy files to colchicifolium to a directory
 `/srv/collector.torproject.org/collector/in/bridge-pool-
 assignments/polyanthum/`. I'll take care of the CollecTor side of things
 then which includes reverting an earlier commit and refreshing that enough
 to run again. 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] #29480 [Circumvention/BridgeDB]: Expose bridge pool assignments again

[Tor Bug Tracker & Wiki]

#29480: Expose bridge pool assignments again
+---
 Reporter:  irl |  Owner:  phw
 Type:  defect  | Status:  needs_information
 Priority:  Medium  |  Milestone:
Component:  Circumvention/BridgeDB  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+---
Changes (by phw):

 * status:  assigned => needs_information


Comment:

 Glancing at [https://collector.torproject.org/archive/bridge-pool-
 assignments/ archived bridge pool assignments], the format does not seem
 to have changed. #14082's description mentions that these files were once
 rsynced over to metrics. I'm happy to set up a cronjob on polyanthum to
 make that happen again.

--
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] #29480 [Circumvention/BridgeDB]: Expose bridge pool assignments again

[Tor Bug Tracker & Wiki]

#29480: Expose bridge pool assignments again
+--
 Reporter:  irl |  Owner:  phw
 Type:  defect  | Status:  assigned
 Priority:  Medium  |  Milestone:
Component:  Circumvention/BridgeDB  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--

Comment (by phw):

 Replying to [comment:5 phw]:
 > I agree. I'm happy to flip the switch and have BridgeDB expose the
 assignments again. Is there anything else that's needed from the metrics
 side?
 [[br]]
 It looks like BridgeDB
 
[https://gitweb.torproject.org/bridgedb.git/commit/?id=f4d559197e06bc4b2e783634d6e79232a440025f
 changed a bit] since metrics last archived these files.  What file format
 were you dealing with? And how did you get access to the assignments file?

 What BridgeDB currently has is an assignments.log file that is structured
 as follows:
 {{{
 bridge-pool-assignment 2019-07-24 00:00:10
 C042E360BB0139ABA8C115A61CAC4F5A65D86A9B moat ip=4 ring=2
 7A95FB316A8D6FE64F24F1742DE066EEBF04A930 moat ip=4,6 ring=2 flag=stable
 transport=websocket,fte,obfs3,scramblesuit,obfs4
 6CC4EC0313D2D823EC2AEF5F5179579F09CB48B0 moat ip=4 ring=2 transport=obfs4
 ...
 }}}

--
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] #29480 [Circumvention/BridgeDB]: Expose bridge pool assignments again

[Tor Bug Tracker & Wiki]

#29480: Expose bridge pool assignments again
+--
 Reporter:  irl |  Owner:  phw
 Type:  defect  | Status:  assigned
 Priority:  Medium  |  Milestone:
Component:  Circumvention/BridgeDB  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by phw):

 * owner:  sysrqb => phw
 * priority:  Very Low => Medium
 * status:  new => assigned


Comment:

 Replying to [comment:4 arma]:
 > I think this would be a really useful step to take -- especially if we
 then list the distribution bucket in relay-search, so operators can learn
 how their bridge is being used (which will in turn help them understand
 why it has the load patterns that it has).
 [[br]]
 I agree. I'm happy to flip the switch and have BridgeDB expose the
 assignments again. Is there anything else that's needed from the metrics
 side?

--
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] #29480 [Circumvention/BridgeDB]: Expose bridge pool assignments again

[Tor Bug Tracker & Wiki]

#29480: Expose bridge pool assignments again
+
 Reporter:  irl |  Owner:  sysrqb
 Type:  defect  | Status:  new
 Priority:  Very Low|  Milestone:
Component:  Circumvention/BridgeDB  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+

Comment (by arma):

 I think this would be a really useful step to take -- especially if we
 then list the distribution bucket in relay-search, so operators can learn
 how their bridge is being used (which will in turn help them understand
 why it has the load patterns that it has).

--
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