Re: [tor-bugs] #30941 [Circumvention/BridgeDB]: Need better instructions for requesting bridges via email

2020-04-07 Thread Tor Bug Tracker & Wiki
#30941: Need better instructions for requesting bridges via email
-+-
 Reporter:  pili |  Owner:  phw
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Circumvention/BridgeDB   |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  ux-team, s30-o22a2, anti-|  Actual Points:  1
  censorship-roadmap-2020Q1  |
Parent ID:  #31279   | Points:  1
 Reviewer:  cohosh   |Sponsor:
 |  Sponsor30
-+-

Comment (by phw):

 Roger suggested to abandon the concept of transport `TYPE`s for now
 because we only offer obfs4 anyway. I addressed his suggestion in commit
 
[https://gitweb.torproject.org/bridgedb.git/commit/?h=develop=208b49cd91ec64aaff623dfeef08d352beab6785
 208b49c] and deployed the fix. BridgeDB's email response now looks as
 follows:

 {{{
 [This is an automated email.]

 Here are your bridges:

   obfs4 ...
   obfs4 ...

 Add these bridges to your Tor Browser by opening your browser
 preferences, clicking on "Tor", and then adding them to the "Provide a
 bridge" field.

 If these bridges are not what you need, reply to this email with one of
 the following commands in the message body:

   get bridges(Request unobfuscated Tor bridges.)
   get ipv6   (Request IPv6 bridges.)
   get transport obfs4(Request obfs4 obfuscated bridges.)
   get key(Get a copy of BridgeDB's public GnuPG key.)
 }}}

--
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] #30941 [Circumvention/BridgeDB]: Need better instructions for requesting bridges via email

2020-04-06 Thread Tor Bug Tracker & Wiki
#30941: Need better instructions for requesting bridges via email
-+-
 Reporter:  pili |  Owner:  phw
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Circumvention/BridgeDB   |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  ux-team, s30-o22a2, anti-|  Actual Points:  1
  censorship-roadmap-2020Q1  |
Parent ID:  #31279   | Points:  1
 Reviewer:  cohosh   |Sponsor:
 |  Sponsor30
-+-
Changes (by phw):

 * status:  merge_ready => closed
 * resolution:   => fixed
 * actualpoints:   => 1


Comment:

 Thanks,
 
[https://gitweb.torproject.org/bridgedb.git/commit/?h=develop=bca64964a255cf959489c7049c66e5eb70b5291c
 merged into develop].

 While inspecting BridgeDB's logs, I noticed that the autoresponder breaks
 when dealing with a quoted response from Gmail's web interface.  I filed
 #33835 to get that fixed.

--
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] #30941 [Circumvention/BridgeDB]: Need better instructions for requesting bridges via email

2020-04-03 Thread Tor Bug Tracker & Wiki
#30941: Need better instructions for requesting bridges via email
-+-
 Reporter:  pili |  Owner:  phw
 Type:  defect   | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:
Component:  Circumvention/BridgeDB   |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ux-team, s30-o22a2, anti-|  Actual Points:
  censorship-roadmap-2020Q1  |
Parent ID:  #31279   | Points:  1
 Reviewer:  cohosh   |Sponsor:
 |  Sponsor30
-+-
Changes (by cohosh):

 * status:  needs_review => merge_ready


Comment:

 This looks great!

--
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] #30941 [Circumvention/BridgeDB]: Need better instructions for requesting bridges via email

2020-04-01 Thread Tor Bug Tracker & Wiki
#30941: Need better instructions for requesting bridges via email
-+-
 Reporter:  pili |  Owner:  phw
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:
Component:  Circumvention/BridgeDB   |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ux-team, s30-o22a2, anti-|  Actual Points:
  censorship-roadmap-2020Q1  |
Parent ID:  #31279   | Points:  1
 Reviewer:  cohosh   |Sponsor:
 |  Sponsor30
-+-
Changes (by phw):

 * status:  assigned => needs_review


Comment:

 I have a fix in my
 
[https://github.com/NullHypothesis/bridgedb/compare/develop...defect/30941?expand=1
 defect/30941] branch. Here's what the code does:

 * Respond with obfs4 (or whatever is configured in `DEFAULT_TRANSPORT`)
 bridges if the user's request is invalid or empty.
 * Remove the help email (which you would previously get after sending an
 invalid request or a request that contains "get help") because we no
 longer need it.
 * Simplify the automatic response as discussed above in this ticket.
 * Make it clear that the email response is automatically generated as
 [https://trac.torproject.org/projects/tor/ticket/30941#comment:16 cohosh
 suggested].

 Here's what BridgeDB's new email response will look like:
 {{{
 [This is an automated email.  Please do not reply.]

 Here are your bridges:

 obfs4 1.1.1.1: ...
 obfs4 2.2.2.2: ...

 Add these bridges to your Tor Browser by opening your browser
 preferences, clicking on "Tor", and then adding them to the "Provide a
 bridge" field.

 If these bridges are not what you need, reply to this email with one of
 the following commands in the message body:

   get bridges(Request unobfuscated Tor bridges.)
   get ipv6   (Request IPv6 bridges.)
   get transport TYPE (Request obfuscated bridges. Replace TYPE with
 'obfs4'.)
   get key(Get a copy of BridgeDB's public GnuPG key.)
 }}}
 Note that "get key" is still supported but we will get rid of this
 functionality in #17548.

--
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] #30941 [Circumvention/BridgeDB]: Need better instructions for requesting bridges via email

2020-03-27 Thread Tor Bug Tracker & Wiki
#30941: Need better instructions for requesting bridges via email
-+-
 Reporter:  pili |  Owner:  phw
 Type:  defect   | Status:
 |  assigned
 Priority:  Medium   |  Milestone:
Component:  Circumvention/BridgeDB   |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ux-team, s30-o22a2, anti-|  Actual Points:
  censorship-roadmap-2020Q1  |
Parent ID:  #31279   | Points:  1
 Reviewer:  cohosh   |Sponsor:
 |  Sponsor30
-+-
Changes (by phw):

 * owner:  sysrqb => phw
 * status:  merge_ready => assigned
 * points:   => 1


Comment:

 I'm changing the status back to 'assigned' because I have yet to write the
 code. :)

--
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] #30941 [Circumvention/BridgeDB]: Need better instructions for requesting bridges via email

2020-03-26 Thread Tor Bug Tracker & Wiki
#30941: Need better instructions for requesting bridges via email
-+-
 Reporter:  pili |  Owner:  sysrqb
 Type:  defect   | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:
Component:  Circumvention/BridgeDB   |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ux-team, s30-o22a2, anti-|  Actual Points:
  censorship-roadmap-2020Q1  |
Parent ID:  #31279   | Points:
 Reviewer:  cohosh   |Sponsor:
 |  Sponsor30
-+-
Changes (by cohosh):

 * status:  needs_review => merge_ready


Comment:

 Replying to [comment:13 phw]:
 > Replying to [comment:8 cohosh]:
 > > - Should we have more text explaining that you issue the commands by
 replying to or sending a new email?
 > [[br]]
 > Hmm, doesn't the email already say that? Please let me know if you would
 like to rephrase it. Here's my latest iteration:
 > {{{
 > Here are your obfs4 bridges:
 >
 >  obfs4 1.2.3.4:1234 ...
 >  obfs4 4.3.2.1:4321 ...
 >
 > Add these bridges to your Tor Browser by opening your browser
 > preferences, clicking on "Tor", and then adding them to the "Provide a
 > bridge" field.
 >
 > If these bridges are not what you need, reply to this email with one of
 > the following commands in the message body:
 >
 >   get transport TYPE(Request obfuscated bridges. Replace
 >  TYPE with "obfs4".)
 >   get bridges   (Request unobfuscated Tor bridges.)
 >   get ipv6  (Request IPv6 bridges.)
 > }}}
 >
 > I also replaced "vanilla" with "unobfuscated" as per teor's suggestion.

 Oh, you're right! This looks good to me. The only other piece of feedback
 is something that came up in a similar GetTor ticket: #23226 to make clear
 in the email text that this is an automated response.

--
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] #30941 [Circumvention/BridgeDB]: Need better instructions for requesting bridges via email

2020-03-26 Thread Tor Bug Tracker & Wiki
#30941: Need better instructions for requesting bridges via email
-+-
 Reporter:  pili |  Owner:  sysrqb
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:
Component:  Circumvention/BridgeDB   |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ux-team, s30-o22a2, anti-|  Actual Points:
  censorship-roadmap-2020Q1  |
Parent ID:  #31279   | Points:
 Reviewer:  cohosh   |Sponsor:
 |  Sponsor30
-+-
Changes (by cohosh):

 * reviewer:   => cohosh


--
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] #30941 [Circumvention/BridgeDB]: Need better instructions for requesting bridges via email

2020-03-25 Thread Tor Bug Tracker & Wiki
#30941: Need better instructions for requesting bridges via email
-+-
 Reporter:  pili |  Owner:  sysrqb
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:
Component:  Circumvention/BridgeDB   |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ux-team, s30-o22a2, anti-|  Actual Points:
  censorship-roadmap-2020Q1  |
Parent ID:  #31279   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor30
-+-

Comment (by phw):

 Replying to [comment:9 teor]:
 > > I suggest that BridgeDB should respond with obfs4 bridges even if the
 email request is invalid
 >
 > Careful with responding to invalid input: it can enable some kinds of
 attacks.
 >
 > I can't think of any attacks that are easier than "just send another,
 correctly-formatted email". But there can sometimes be risks with email
 forwarding, or mailing lists.
 [[br]]
 BridgeDB already is responding to invalid emails with help instructions. I
 think the benefits of this behaviour (it helps confused users) outweighs
 the harm you mentioned – at least so far.

--
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] #30941 [Circumvention/BridgeDB]: Need better instructions for requesting bridges via email

2020-03-25 Thread Tor Bug Tracker & Wiki
#30941: Need better instructions for requesting bridges via email
-+-
 Reporter:  pili |  Owner:  sysrqb
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:
Component:  Circumvention/BridgeDB   |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ux-team, s30-o22a2, anti-|  Actual Points:
  censorship-roadmap-2020Q1  |
Parent ID:  #31279   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor30
-+-
Changes (by phw):

 * status:  needs_information => needs_review


Comment:

 Replying to [comment:8 cohosh]:
 > - Are we still handing out FTE or scramblesuit bridges? From what i
 remember, we removed default FTE bridges from Tor Browser awhile ago. I
 guess the same could be asked of obfs3. If we only care about handing out
 obfs4, there's some simplification that can be done with the instructions
 here.
 [[br]]
 Since #33299 we no longer are.  At this point, the only PT is obfs4.
 [[br]]
 > - Should we have more text explaining that you issue the commands by
 replying to or sending a new email?
 [[br]]
 Hmm, doesn't the email already say that? Please let me know if you would
 like to rephrase it. Here's my latest iteration:
 {{{
 Here are your obfs4 bridges:

  obfs4 1.2.3.4:1234 ...
  obfs4 4.3.2.1:4321 ...

 Add these bridges to your Tor Browser by opening your browser
 preferences, clicking on "Tor", and then adding them to the "Provide a
 bridge" field.

 If these bridges are not what you need, reply to this email with one of
 the following commands in the message body:

   get transport TYPE(Request obfuscated bridges. Replace
  TYPE with "obfs4".)
   get bridges   (Request unobfuscated Tor bridges.)
   get ipv6  (Request IPv6 bridges.)
 }}}

 I also replaced "vanilla" with "unobfuscated" as per teor's suggestion.

--
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] #30941 [Circumvention/BridgeDB]: Need better instructions for requesting bridges via email

2020-03-05 Thread Tor Bug Tracker & Wiki
#30941: Need better instructions for requesting bridges via email
-+-
 Reporter:  pili |  Owner:  sysrqb
 Type:  defect   | Status:
 |  needs_information
 Priority:  Medium   |  Milestone:
Component:  Circumvention/BridgeDB   |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ux-team, s30-o22a2, anti-|  Actual Points:
  censorship-roadmap-2020Q1  |
Parent ID:  #31279   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor30
-+-
Changes (by cohosh):

 * cc: cohosh (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] #30941 [Circumvention/BridgeDB]: Need better instructions for requesting bridges via email

2020-02-18 Thread Tor Bug Tracker & Wiki
#30941: Need better instructions for requesting bridges via email
-+-
 Reporter:  pili |  Owner:  sysrqb
 Type:  defect   | Status:
 |  needs_information
 Priority:  Medium   |  Milestone:
Component:  Circumvention/BridgeDB   |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ux-team, s30-o22a2, anti-|  Actual Points:
  censorship-roadmap-2020Q1  |
Parent ID:  #31279   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor30
-+-

Comment (by phw):

 When rephrasing the email response, let's keep in mind that we're retiring
 obfs3, scramblesuit, and fte (see #33299).

--
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] #30941 [Circumvention/BridgeDB]: Need better instructions for requesting bridges via email

2020-02-13 Thread Tor Bug Tracker & Wiki
#30941: Need better instructions for requesting bridges via email
-+-
 Reporter:  pili |  Owner:  sysrqb
 Type:  defect   | Status:
 |  needs_information
 Priority:  Medium   |  Milestone:
Component:  Circumvention/BridgeDB   |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ux-team, s30-o22a2, anti-|  Actual Points:
  censorship-roadmap-2020Q1  |
Parent ID:  #31279   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor30
-+-

Comment (by teor):

 As far as the text itself goes, the following words are ambiguous:
 * vanilla
 * several
 * plain-ol'-vanilla
 * cool

 We should replace them with simpler English words, to help people who
 don't use our dialect of English.

--
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] #30941 [Circumvention/BridgeDB]: Need better instructions for requesting bridges via email

2020-02-13 Thread Tor Bug Tracker & Wiki
#30941: Need better instructions for requesting bridges via email
-+-
 Reporter:  pili |  Owner:  sysrqb
 Type:  defect   | Status:
 |  needs_information
 Priority:  Medium   |  Milestone:
Component:  Circumvention/BridgeDB   |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ux-team, s30-o22a2, anti-|  Actual Points:
  censorship-roadmap-2020Q1  |
Parent ID:  #31279   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor30
-+-

Comment (by teor):

 > I suggest that BridgeDB should respond with obfs4 bridges even if the
 email request is invalid

 Careful with responding to invalid input: it can enable some kinds of
 attacks.

 I can't think of any attacks that are easier than "just send another,
 correctly-formatted email". But there can sometimes be risks with email
 forwarding, or mailing lists.

--
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] #30941 [Circumvention/BridgeDB]: Need better instructions for requesting bridges via email

2020-02-06 Thread Tor Bug Tracker & Wiki
#30941: Need better instructions for requesting bridges via email
-+-
 Reporter:  pili |  Owner:  sysrqb
 Type:  defect   | Status:
 |  needs_information
 Priority:  Medium   |  Milestone:
Component:  Circumvention/BridgeDB   |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ux-team, s30-o22a2, anti-|  Actual Points:
  censorship-roadmap-2020Q1  |
Parent ID:  #31279   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor30
-+-
Changes (by cohosh):

 * status:  needs_review => needs_information


Comment:

 Nice! I think we should ask antonela to look over this as well. I like the
 changes. Some comments:

 - The idea to provide bridges on failure is really nice. I like how you've
 structured that email.

 - Are we still handing out FTE or scramblesuit bridges? From what i
 remember, we removed default FTE bridges from Tor Browser awhile ago. I
 guess the same could be asked of obfs3. If we only care about handing out
 obfs4, there's some simplification that can be done with the instructions
 here.

 - Should we have more text explaining that you issue the commands by
 replying to or sending a new email?

--
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] #30941 [Circumvention/BridgeDB]: Need better instructions for requesting bridges via email

2020-02-04 Thread Tor Bug Tracker & Wiki
#30941: Need better instructions for requesting bridges via email
-+-
 Reporter:  pili |  Owner:  sysrqb
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:
Component:  Circumvention/BridgeDB   |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ux-team, s30-o22a2, anti-|  Actual Points:
  censorship-roadmap-2020Q1  |
Parent ID:  #31279   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor30
-+-
Changes (by phw):

 * status:  new => needs_review


Comment:

 Replying to [comment:3 phw]:
 > I agree that we need to overhaul the email distribution method. It took
 me a while too, to first figure out how it works, which is bad. Fixing the
 instructions on bridges.torproject.org is something we can do easily. How
 about we change it to the following:
 >
 > > Another way to get bridges is to send an email to
 brid...@torproject.org. Leave the email subject empty and write "get
 bridges" in the email body for normal bridges or "get transport obfs4" for
 an obfuscated bridge. Please note that you must send the email using an
 address from one of the following email providers: Riseup or Gmail.
 [[br]]
 I just deployed this fix as part of #31427. Ticket #17626 is also fixed,
 so what's left is to improve BridgeDB's email instructions. They currently
 say:
 {{{
 Hey, identityfunction! Welcome to BridgeDB!



 COMMANDs: (combine COMMANDs to specify multiple options simultaneously)
   get bridgesRequest vanilla bridges.
   get transport [TYPE]   Request a Pluggable Transport by TYPE.
   get help   Displays this message.
   get keyGet a copy of BridgeDB's public GnuPG key.
   get ipv6   Request IPv6 bridges.

 Currently supported transport TYPEs:
   fte
   obfs3
   obfs4
   scramblesuit


 BridgeDB can provide bridges with several types of Pluggable
 Transports[0],
 which can help obfuscate your connections to the Tor Network, making it
 more
 difficult for anyone watching your internet traffic to determine that you
 are
 using Tor.

 Some bridges with IPv6 addresses are also available, though some Pluggable
 Transports aren't IPv6 compatible.

 Additionally, BridgeDB has plenty of plain-ol'-vanilla bridges - without
 any
 Pluggable Transports - which maybe doesn't sound as cool, but they can
 still
 help to circumvent internet censorship in many cases.

 [0]: https://www.torproject.org/docs/pluggable-transports.html

  --
  <3 BridgeDB
 }}}

 I suggest that BridgeDB should respond with obfs4 bridges even if the
 email request is invalid:

 {{{
 Here are your obfs4 bridges:

  obfs4 1.2.3.4:1234 ...
  obfs4 4.3.2.1:4321 ...

 Add these bridges to your Tor Browser by opening your browser
 preferences, clicking on "Tor", and then adding them to the "Provide a
 bridge" field.

 If these bridges are not what you need, respond to this email with one
 of the following commands in the message body:

   get bridges   (Request "vanilla" Tor bridges.)
   get transport TYPE(Request a different obfuscation type. Replace
  TYPE with obfs3, obfs4, or scramblesuit.)
   get ipv6  (Request IPv6 bridges.)
 }}}

 What do you think? How can we make it better?

--
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] #30941 [Circumvention/BridgeDB]: Need better instructions for requesting bridges via email

2020-02-04 Thread Tor Bug Tracker & Wiki
#30941: Need better instructions for requesting bridges via email
-+-
 Reporter:  pili |  Owner:  sysrqb
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Circumvention/BridgeDB   |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ux-team, s30-o22a2, anti-|  Actual Points:
  censorship-roadmap-2020Q1  |
Parent ID:  #31279   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor30
-+-
Changes (by gaba):

 * keywords:  ux-team, s30-o22a2 => ux-team, s30-o22a2, anti-censorship-
 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] #30941 [Circumvention/BridgeDB]: Need better instructions for requesting bridges via email

2019-08-05 Thread Tor Bug Tracker & Wiki
#30941: Need better instructions for requesting bridges via email
+---
 Reporter:  pili|  Owner:  sysrqb
 Type:  defect  | Status:  new
 Priority:  Medium  |  Milestone:
Component:  Circumvention/BridgeDB  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  ux-team |  Actual Points:
Parent ID:  #31279  | Points:
 Reviewer:  |Sponsor:  Sponsor30
+---
Changes (by pili):

 * parent:   => #31279


--
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] #30941 [Circumvention/BridgeDB]: Need better instructions for requesting bridges via email

2019-07-02 Thread Tor Bug Tracker & Wiki
#30941: Need better instructions for requesting bridges via email
+---
 Reporter:  pili|  Owner:  sysrqb
 Type:  defect  | Status:  new
 Priority:  Medium  |  Milestone:
Component:  Circumvention/BridgeDB  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  ux-team |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:  Sponsor30
+---
Changes (by phw):

 * cc: phw (added)


Comment:

 Replying to [comment:1 pili]:
 > P.s I finally figured out that the body content has to be empty apart
 from the command... (previously I was just replying to the original email,
 keeping the conversation history in the body)
 [[br]]
 This issue is documented over in #17626.

 I agree that we need to overhaul the email distribution method. It took me
 a while too, to first figure out how it works, which is bad. Fixing the
 instructions on bridges.torproject.org is something we can do easily. How
 about we change it to the following:

 > Another way to get bridges is to send an email to
 brid...@torproject.org. Leave the email subject empty and write "get
 bridges" in the email body for normal bridges or "get transport obfs4" for
 an obfuscated bridge. Please note that you must send the email using an
 address from one of the following email providers: Riseup or Gmail.

--
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] #30941 [Circumvention/BridgeDB]: Need better instructions for requesting bridges via email

2019-06-21 Thread Tor Bug Tracker & Wiki
#30941: Need better instructions for requesting bridges via email
+---
 Reporter:  pili|  Owner:  sysrqb
 Type:  defect  | Status:  new
 Priority:  Medium  |  Milestone:
Component:  Circumvention/BridgeDB  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  ux-team |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:  Sponsor30
+---

Comment (by antonela):

 Yes, requesting bridges is painful right now. I suggested a usable
 solution for it in #30456.

--
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] #30941 [Circumvention/BridgeDB]: Need better instructions for requesting bridges via email

2019-06-21 Thread Tor Bug Tracker & Wiki
#30941: Need better instructions for requesting bridges via email
+---
 Reporter:  pili|  Owner:  sysrqb
 Type:  defect  | Status:  new
 Priority:  Medium  |  Milestone:
Component:  Circumvention/BridgeDB  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  ux-team |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:  Sponsor30
+---

Comment (by pili):

 P.s I finally figured out that the body content has to be empty apart from
 the command... (previously I was just replying to the original email,
 keeping the conversation history in the body)

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

[tor-bugs] #30941 [Circumvention/BridgeDB]: Need better instructions for requesting bridges via email

2019-06-21 Thread Tor Bug Tracker & Wiki
#30941: Need better instructions for requesting bridges via email
+-
 Reporter:  pili|  Owner:  sysrqb
 Type:  defect  | Status:  new
 Priority:  Medium  |  Milestone:
Component:  Circumvention/BridgeDB  |Version:
 Severity:  Normal  |   Keywords:  ux-team
Actual Points:  |  Parent ID:
   Points:  |   Reviewer:
  Sponsor:  Sponsor30   |
+-
 For bridges obtained via email by emailing bridges@ it's not clear
 how/where to request bridges via email.

 E.g the bridges.tpo website simply says to email bridges@ to get bridges

 Emailing that address gives you a number of commands but doesn't specify
 where to send the commands (email subject, body...) I tried both and
 wasn't able to get it to work.

 It also specifies that you can combine commands but it doesn't give any
 examples or indication of how to do so.

 This was raised by a user and I also couldn't figure it out after trying
 for about 5 minutes :/

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