[tor-bugs] #29128 [Core Tor/Tor]: Place complete obfs4 bridge line in accessible location

[Tor Bug Tracker & Wiki]

#29128: Place complete obfs4 bridge line in accessible location
--+
 Reporter:  phoul |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 Currently operators wanting to distribute or use personal obfs4 bridges
 must follow 5 steps:

 1. Determine their bridge's IP address
 2. Check logs for their bridge's fingerprint
 3. Check logs for which port obfs4 is running on
 4. Retrieve their obfs4 cert from
 /var/lib/tor/pt_state/obfs4_bridgeline.txt
 5. String the above together in the following format:

 {{{
 Bridge obfs4 :  cert=$FROMSTEP4 iat-mode=0
 }}}

 This can be a confusing process, and is only fully explained upon opening
 `/var/lib/tor/pt_state/obfs4_bridgeline.txt`; however it leaves filling in
 the fields (with the exception of the cert) to the user.

 Having the complete bridge line placed somewhere accessible would make
 this process much less painful for operators.

--
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] #29128 [Core Tor/Tor]: Place complete obfs4 bridge line in accessible location

[Tor Bug Tracker & Wiki]

#29128: Place complete obfs4 bridge line in accessible location
-+-
 Reporter:  phoul|  Owner:  (none)
 Type:  defect   | Status:
 |  needs_information
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-pt, tor-doc, |  Actual Points:
  040-deferred-20190220  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by cohosh):

 * cc: cohosh (added)


Comment:

 A duplicate ticket #30331 was filed about this recently

--
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] #29128 [Core Tor/Tor]: Place complete obfs4 bridge line in accessible location

[Tor Bug Tracker & Wiki]

#29128: Place complete obfs4 bridge line in accessible location
-+-
 Reporter:  phoul|  Owner:  (none)
 Type:  defect   | Status:
 |  needs_information
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-pt, tor-doc, |  Actual Points:
  040-deferred-20190220  |
Parent ID:  #30471   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by phw):

 * parent:   => #30471


--
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] #29128 [Core Tor/Tor]: Place complete obfs4 bridge line in accessible location

[Tor Bug Tracker & Wiki]

#29128: Place complete obfs4 bridge line in accessible location
-+-
 Reporter:  phoul|  Owner:  (none)
 Type:  defect   | Status:
 |  needs_information
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-pt, tor-doc, |  Actual Points:
  040-deferred-20190220  |
Parent ID:  #30471   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by phw):

 Over in #30331, it was suggested to either log the full bridge line, or
 write it to something like $DATADIR/pt_state/bridgelines.txt, along with
 all other PTs that the bridge runs. The problem with a log message is that
 bridge operators may accidentally publish their bridge when they paste
 their logs, e.g., here on trac.

 I suppose a bridge could write to bridgelines.txt before it publishes its
 descriptor because that's when all the necessary information is available?

--
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] #29128 [Core Tor/Tor]: Place complete obfs4 bridge line in accessible location

[Tor Bug Tracker & Wiki]

#29128: Place complete obfs4 bridge line in accessible location
-+-
 Reporter:  phoul|  Owner:  (none)
 Type:  defect   | Status:
 |  needs_information
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-pt, tor-doc, |  Actual Points:
  040-deferred-20190220  |
Parent ID:  #30471   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by phw):

 * cc: phw (added)


--
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] #29128 [Core Tor/Tor]: Place complete obfs4 bridge line in accessible location

[Tor Bug Tracker & Wiki]

#29128: Place complete obfs4 bridge line in accessible location
-+
 Reporter:  phoul|  Owner:  (none)
 Type:  defect   | Status:  needs_information
 Priority:  Medium   |  Milestone:  Tor: 0.4.0.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-pt, tor-doc  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+
Changes (by dgoulet):

 * status:  new => needs_information
 * keywords:   => tor-pt, tor-doc
 * milestone:   => Tor: 0.4.0.x-final


Comment:

 What do you mean "accessible" here? If it is not in `pt_state/` then it
 has to be at the very least at the root of the Tor data directory. Seems
 to me that we should probably update our documentation to tell the
 operator where to find that line?

--
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] #29128 [Core Tor/Tor]: Place complete obfs4 bridge line in accessible location

[Tor Bug Tracker & Wiki]

#29128: Place complete obfs4 bridge line in accessible location
-+
 Reporter:  phoul|  Owner:  (none)
 Type:  defect   | Status:  needs_information
 Priority:  Medium   |  Milestone:  Tor: 0.4.0.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-pt, tor-doc  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+

Comment (by phoul):

 The complete line is not placed anywhere currently, only instructions for
 forming it yourself are present in
 /var/lib/tor/pt_state/obfs4_bridgeline.txt (and the cert portion of the
 bridge line).

 This has caused confusion, and it was requested that the complete line be
 placed somewhere so operators can copy/paste without having to fill in the
 blanks on their own. It was also mentioned on IRC that it might be
 desirable to have this printed in the tor log, along with the other bridge
 details.

--
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] #29128 [Core Tor/Tor]: Place complete obfs4 bridge line in accessible location

[Tor Bug Tracker & Wiki]

#29128: Place complete obfs4 bridge line in accessible location
-+-
 Reporter:  phoul|  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-pt, tor-doc, |  Actual Points:
  040-deferred-20190220, network-team-roadmap-   |
  2020Q1 |
Parent ID:  #30471   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor28-must
-+-
Changes (by gaba):

 * keywords:  tor-pt, tor-doc, 040-deferred-20190220, network-team-roadmap-
 november => tor-pt, tor-doc, 040-deferred-20190220, network-team-
 roadmap-2020Q1


--
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] #29128 [Core Tor/Tor]: Place complete obfs4 bridge line in accessible location

[Tor Bug Tracker & Wiki]

#29128: Place complete obfs4 bridge line in accessible location
-+-
 Reporter:  phoul|  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-pt, tor-doc, |  Actual Points:
  040-deferred-20190220, network-team-roadmap-   |
  2020Q1 |
Parent ID:  #30471   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor28-must
-+-
Changes (by catalyst):

 * cc: catalyst (added)


--
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] #29128 [Core Tor/Tor]: Place complete obfs4 bridge line in accessible location

[Tor Bug Tracker & Wiki]

#29128: Place complete obfs4 bridge line in accessible location
-+-
 Reporter:  phoul|  Owner:
 |  catalyst
 Type:  defect   | Status:
 |  assigned
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-pt, tor-doc, |  Actual Points:
  040-deferred-20190220, network-team-roadmap-   |
  2020Q1 |
Parent ID:  #30471   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor28-must
-+-
Changes (by gaba):

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


--
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] #29128 [Core Tor/Tor]: Place complete obfs4 bridge line in accessible location

[Tor Bug Tracker & Wiki]

#29128: Place complete obfs4 bridge line in accessible location
-+-
 Reporter:  phoul|  Owner:
 |  catalyst
 Type:  defect   | Status:
 |  assigned
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-pt, tor-doc, |  Actual Points:
  040-deferred-20190220, network-team-roadmap-   |
  2020Q1, network-team-roadmap-2020Q2|
Parent ID:  #30471   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor28-must
-+-

Comment (by catalyst):

 Scope question: do we want to do this for non-PT bridges as well? More
 generally, any ideas about a reasonable stage of startup or periodic tasks
 to do it?

--
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] #29128 [Core Tor/Tor]: Place complete obfs4 bridge line in accessible location

[Tor Bug Tracker & Wiki]

#29128: Place complete obfs4 bridge line in accessible location
-+-
 Reporter:  phoul|  Owner:
 |  catalyst
 Type:  defect   | Status:
 |  assigned
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-pt, tor-doc, |  Actual Points:
  040-deferred-20190220, network-team-roadmap-   |
  2020Q1, network-team-roadmap-2020Q2|
Parent ID:  #30471   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor28-must
-+-

Comment (by teor):

 On IRC, catalyst said that pt_get_extra_info_descriptor_string() doesn't
 completely support IPv6. It looks like that's a known issue, see #7961.

 For IPv6, you can use the router_get_advertised_ipv6_or_ap() function. But
 I'm not sure which tor version we added the function in.

 See also #31009, where we replace internal IP addresses in descriptors,
 with the published IP address. We should make sure that fix also gets
 written to this file.

--
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] #29128 [Core Tor/Tor]: Place complete obfs4 bridge line in accessible location

[Tor Bug Tracker & Wiki]

#29128: Place complete obfs4 bridge line in accessible location
-+-
 Reporter:  phoul|  Owner:
 |  catalyst
 Type:  defect   | Status:
 |  assigned
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.4.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-pt, tor-doc, |  Actual Points:
  040-deferred-20190220, network-team-roadmap-   |
  2020Q1, network-team-roadmap-2020Q2|
  anticensorship-wants 044-should?   |
Parent ID:  #30471   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor28-must
-+-
Changes (by nickm):

 * keywords:
 tor-pt, tor-doc, 040-deferred-20190220, network-team-roadmap-2020Q1,
 network-team-roadmap-2020Q2
 =>
 tor-pt, tor-doc, 040-deferred-20190220, network-team-roadmap-2020Q1,
 network-team-roadmap-2020Q2 anticensorship-wants 044-should?
 * milestone:  Tor: unspecified => Tor: 0.4.4.x-final


--
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] #29128 [Core Tor/Tor]: Place complete obfs4 bridge line in accessible location

[Tor Bug Tracker & Wiki]

#29128: Place complete obfs4 bridge line in accessible location
-+-
 Reporter:  phoul|  Owner:  (none)
 Type:  defect   | Status:
 |  needs_information
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-pt, tor-doc, |  Actual Points:
  040-deferred-20190220  |
Parent ID:  #30471   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by phw):

 We briefly discussed this in [http://meetbot.debian.net/tor-meeting/2019
 /tor-meeting.2019-06-20-17.00.log.html today's anti-censorship meeting].
 We believe that tor should create its bridge lines and write it to a file
 in its data directory, e.g., `bridges-lines`. We believe that `pt_state/`
 should be reserved for pluggable transports.

--
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] #29128 [Core Tor/Tor]: Place complete obfs4 bridge line in accessible location

[Tor Bug Tracker & Wiki]

#29128: Place complete obfs4 bridge line in accessible location
-+-
 Reporter:  phoul|  Owner:  (none)
 Type:  defect   | Status:
 |  needs_information
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-pt, tor-doc, |  Actual Points:
  040-deferred-20190220  |
Parent ID:  #30471   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by nickm):

 Is there a standardized way for Tor to learn from the PT which fields it
 should put in the Bridge line?  It knows the `fingerprint`, and it has a
 good guess about the `address` field (though the PT may want to override
 that), but it  usually needs the PT's help to learn the `port` and any
 other fields.

--
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] #29128 [Core Tor/Tor]: Place complete obfs4 bridge line in accessible location

[Tor Bug Tracker & Wiki]

#29128: Place complete obfs4 bridge line in accessible location
-+-
 Reporter:  phoul|  Owner:  (none)
 Type:  defect   | Status:
 |  needs_information
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-pt, tor-doc, |  Actual Points:
  040-deferred-20190220  |
Parent ID:  #30471   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor28
-+-
Changes (by pili):

 * sponsor:   => Sponsor28


--
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] #29128 [Core Tor/Tor]: Place complete obfs4 bridge line in accessible location

[Tor Bug Tracker & Wiki]

#29128: Place complete obfs4 bridge line in accessible location
-+-
 Reporter:  phoul|  Owner:  (none)
 Type:  defect   | Status:
 |  needs_information
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-pt, tor-doc, |  Actual Points:
  040-deferred-20190220  |
Parent ID:  #30471   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor28
-+-

Comment (by phw):

 Replying to [comment:9 nickm]:
 > Is there a standardized way for Tor to learn from the PT which fields it
 should put in the Bridge line?  It knows the `fingerprint`, and it has a
 good guess about the `address` field (though the PT may want to override
 that), but it  usually needs the PT's help to learn the `port` and any
 other fields.
 [[br]]
 I believe that all we need is in the `SMETHOD` line that Tor reads from
 the PT proxy's stdout. Our [https://gitweb.torproject.org/torspec.git/tree
 /pt-spec.txt#n544 pt-spec.txt] documents its format as:
 {{{
 SMETHOD   [options]
 }}}
 Note that `[options]` will need a bit of processing because
 [https://gitweb.torproject.org/torspec.git/tree/pt-spec.txt#n555 it's
 currently defined] as `ARGS:[=,]+[=]`.

--
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] #29128 [Core Tor/Tor]: Place complete obfs4 bridge line in accessible location

[Tor Bug Tracker & Wiki]

#29128: Place complete obfs4 bridge line in accessible location
-+-
 Reporter:  phoul|  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-pt, tor-doc, |  Actual Points:
  040-deferred-20190220  |
Parent ID:  #30471   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor28
-+-
Changes (by teor):

 * status:  needs_information => new


Comment:

 Replying to [comment:11 phw]:
 > Replying to [comment:9 nickm]:
 > > Is there a standardized way for Tor to learn from the PT which fields
 it should put in the Bridge line?  It knows the `fingerprint`, and it has
 a good guess about the `address` field (though the PT may want to override
 that), but it  usually needs the PT's help to learn the `port` and any
 other fields.
 > [[br]]
 > I believe that all we need is in the `SMETHOD` line that Tor reads from
 the PT proxy's stdout.

 The complete PT line is sent to bridge users by BridgeDB.
 (That line *must* contain all the required information, otherwise bridge
 users wouldn't be able to use the bridge.)

 BridgeDB gets bridge PT lines from bridge extra-info document "transport"
 lines:
 https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt#n1211

 These lines come from pt_get_extra_info_descriptor_string(), which you
 should be able to just dump to a file:
 
https://github.com/torproject/tor/blob/989b6325d671744aacec191b181e8b0b0fee35be/src/feature/client/transports.c#L1613

--
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] #29128 [Core Tor/Tor]: Place complete obfs4 bridge line in accessible location

[Tor Bug Tracker & Wiki]

#29128: Place complete obfs4 bridge line in accessible location
-+-
 Reporter:  phoul|  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-pt, tor-doc, |  Actual Points:
  040-deferred-20190220  |
Parent ID:  #30471   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor28-must
-+-
Changes (by gaba):

 * sponsor:  Sponsor28 => Sponsor28-must


--
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] #29128 [Core Tor/Tor]: Place complete obfs4 bridge line in accessible location

[Tor Bug Tracker & Wiki]

#29128: Place complete obfs4 bridge line in accessible location
-+-
 Reporter:  phoul|  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-pt, tor-doc, |  Actual Points:
  040-deferred-20190220, network-team-roadmap-   |
  november   |
Parent ID:  #30471   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor28-must
-+-
Changes (by gaba):

 * keywords:  tor-pt, tor-doc, 040-deferred-20190220 => tor-pt, tor-doc,
 040-deferred-20190220, network-team-roadmap-november


--
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] #29128 [Core Tor/Tor]: Place complete obfs4 bridge line in accessible location

[Tor Bug Tracker & Wiki]

#29128: Place complete obfs4 bridge line in accessible location
-+-
 Reporter:  phoul|  Owner:  (none)
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.5.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-pt, tor-doc, |  Actual Points:
  040-deferred-20190220, network-team-roadmap-   |
  2020Q1, network-team-roadmap-2020Q2|
  anticensorship-wants 044-deferred  |
Parent ID:  #30471   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor28-must
-+-
Changes (by nickm):

 * keywords:
 tor-pt, tor-doc, 040-deferred-20190220, network-team-roadmap-2020Q1,
 network-team-roadmap-2020Q2 anticensorship-wants 044-should?
 =>
 tor-pt, tor-doc, 040-deferred-20190220, network-team-roadmap-2020Q1,
 network-team-roadmap-2020Q2 anticensorship-wants 044-deferred
 * type:  defect => enhancement
 * milestone:  Tor: 0.4.4.x-final => Tor: 0.4.5.x-final


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