Re: [tor-bugs] #32238 [Applications/Tor Browser]: Some websites not loading pictures after upgrade to Tor Browser 9.0

[Tor Bug Tracker & Wiki]

#32238: Some websites not loading pictures after upgrade to Tor Browser 9.0
--+--
 Reporter:  AxBnO3|  Owner:  tbb-team
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:  tbb-9.0-issues|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by cypherpunks):

 \o/ Make it a child of the CF issues metabug, so that everybody can see
 what harm CF can bring to them, and that it's not `tbb-9.0-issues`.

--
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] #32116 [Applications/Tor Browser]: Fix tor-browser's .mozconfig so that ./mach configure succeeds on Linux by default

[Tor Bug Tracker & Wiki]

#32116: Fix tor-browser's .mozconfig so that ./mach configure succeeds on Linux 
by
default
--+---
 Reporter:  pospeselr |  Owner:  pospeselr
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:  TorBrowserTeam201912R |  Actual Points:  0
Parent ID:| Points:  0
 Reviewer:  gk|Sponsor:
--+---
Changes (by gk):

 * status:  needs_review => closed
 * cc: pili (added)
 * resolution:   => fixed


Comment:

 Looks good now, thanks. Merged to `tor-browser-68.3.0esr-9.5-1` (commit
 cb3038cf717f25e759fb3fdc0a8e941dbfc4e0f1).

 FWIW: I don't think this did cost you 0 points, meaning no time, but
 that's a thing Pili needs to decide/raise. :)

--
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] #32238 [Applications/Tor Browser]: Some websites not loading pictures after upgrade to Tor Browser 9.0

[Tor Bug Tracker & Wiki]

#32238: Some websites not loading pictures after upgrade to Tor Browser 9.0
--+--
 Reporter:  AxBnO3|  Owner:  tbb-team
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:  tbb-9.0-issues|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by gk):

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


Comment:

 Cloudflare fixed that on their end. I think we are good now, 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] #32705 [Core Tor/Tor]: check-local tries to run test_practracker.sh even if we have no python

[Tor Bug Tracker & Wiki]

#32705: check-local tries to run test_practracker.sh even if we have no python
+--
 Reporter:  nickm   |  Owner:  teor
 Type:  defect  | Status:  assigned
 Priority:  Medium  |  Milestone:  Tor:
|  0.4.3.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  tor-ci-fail jenkins python  |  Actual Points:
Parent ID:  | Points:  0.1
 Reviewer:  |Sponsor:
+--
Changes (by teor):

 * status:  new => assigned
 * owner:  (none) => teor
 * keywords:  tor-ci jenkins python => tor-ci-fail jenkins python


--
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] #15618 [Core Tor/Tor]: Tried to establish rendezvous on non-OR circuit with purpose Acting as rendevous (pending)

[Tor Bug Tracker & Wiki]

#15618: Tried to establish rendezvous on non-OR circuit with purpose Acting as
rendevous (pending)
-+-
 Reporter:  asn  |  Owner:  (none)
 Type:  defect   | Status:
 |  assigned
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-hs needs-insight needs-  |  Actual Points:
  diagnosis  |
Parent ID:   | Points:  1
 Reviewer:   |Sponsor:
-+-

Comment (by teor):

 Anyone running a recent version of 0.3.5 or later should have #29029,
 which turns this warning into a protocol warning. That change doesn't
 solve the issue, but it makes it quieter for relay operators, who can't do
 anything about 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] #28863 [Core Tor/Fallback Scripts]: updateFallbackDirs.py thinks it is python 3 compatible but it is not

[Tor Bug Tracker & Wiki]

#28863: updateFallbackDirs.py thinks it is python 3 compatible but it is not
---+
 Reporter:  starlight  |  Owner:  (none)
 Type:  defect | Status:  needs_revision
 Priority:  Medium |  Milestone:
Component:  Core Tor/Fallback Scripts  |Version:
 Severity:  Normal | Resolution:
 Keywords:  fallback-ci, 043-must  |  Actual Points:  0.5
Parent ID:  #30971 | Points:
 Reviewer:  asn|Sponsor:
---+
Changes (by teor):

 * status:  needs_review => needs_revision


Comment:

 I need to add future statements at the start of the scripts:
 from __future__ import print_function

 And for the update script:
 from __future__ import division

--
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] #18361 [Applications/Tor Browser]: Issues with corporate censorship and mass surveillance

[Tor Bug Tracker & Wiki]

#18361: Issues with corporate censorship and mass surveillance
--+--
 Reporter:  ioerror   |  Owner:  cypherpunks
 Type:  defect| Status:  assigned
 Priority:  Very High |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Critical  | Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:  1000 light years
 Reviewer:|Sponsor:
--+--

Comment (by cypherpunks):

 @325

 Sorry but we're on strike agaist that repository. Do it yourself.

--
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] #32657 [Circumvention/Snowflake]: Investigate Snowflake blocking in China

[Tor Bug Tracker & Wiki]

#32657: Investigate Snowflake blocking in China
-+---
 Reporter:  cohosh   |  Owner:  cohosh
 Type:  defect   | Status:  needs_information
 Priority:  High |  Milestone:
Component:  Circumvention/Snowflake  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  blocking, china  |  Actual Points:  2
Parent ID:   | Points:
 Reviewer:   |Sponsor:  Sponsor28
-+---
Changes (by cohosh):

 * actualpoints:   => 2


--
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] #31971 [Circumvention/Snowflake]: Snowflake is *consistently* extremely slow when using the Windows build

[Tor Bug Tracker & Wiki]

#31971: Snowflake is *consistently* extremely slow when using the Windows build
-+---
 Reporter:  cypherpunks  |  Owner:  cohosh
 Type:  defect   | Status:  needs_information
 Priority:  Medium   |  Milestone:
Component:  Circumvention/Snowflake  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:  .5
Parent ID:   | Points:  3
 Reviewer:   |Sponsor:  Sponsor28
-+---

Comment (by cohosh):

 I'm running some throughput tests using the attached windows_script.bat
 and windows-torrc files. After 20 runs, I was getting a maximum throughput
 of about 20 KB/s. I'm going to try this on a windows box instead of a VM
 to see if anything changes.

--
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] #31971 [Circumvention/Snowflake]: Snowflake is *consistently* extremely slow when using the Windows build

[Tor Bug Tracker & Wiki]

#31971: Snowflake is *consistently* extremely slow when using the Windows build
-+---
 Reporter:  cypherpunks  |  Owner:  cohosh
 Type:  defect   | Status:  needs_information
 Priority:  Medium   |  Milestone:
Component:  Circumvention/Snowflake  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:  .5
Parent ID:   | Points:  3
 Reviewer:   |Sponsor:  Sponsor28
-+---
Changes (by cohosh):

 * Attachment "windows_script.bat" 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] #31971 [Circumvention/Snowflake]: Snowflake is *consistently* extremely slow when using the Windows build

[Tor Bug Tracker & Wiki]

#31971: Snowflake is *consistently* extremely slow when using the Windows build
-+---
 Reporter:  cypherpunks  |  Owner:  cohosh
 Type:  defect   | Status:  needs_information
 Priority:  Medium   |  Milestone:
Component:  Circumvention/Snowflake  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:  .5
Parent ID:   | Points:  3
 Reviewer:   |Sponsor:  Sponsor28
-+---
Changes (by cohosh):

 * Attachment "windows-torrc" 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] #32552 [Core Tor/Nyx]: stem says "dictionary keys changed during iteration" with new python

[Tor Bug Tracker & Wiki]

#32552: stem says "dictionary keys changed during iteration" with new python
--+--
 Reporter:  cypherpunks   |  Owner:  atagar
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Nyx  |Version:  Tor: 0.4.1.6
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by dave_in_seattle):

 After a lot of failed debugging, I found this thread by googling: tor stem
 dictionary keys changed during iteration.

 I uninstalled Python 3.8 then installed Python 3.7. The problem went away.
 Solved. Thank you!

 I thought I should add my two cents because I'm using Windows 10.

 Stem version: 1.7.1

--
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] #32116 [Applications/Tor Browser]: Fix tor-browser's .mozconfig so that ./mach configure succeeds on Linux by default

[Tor Bug Tracker & Wiki]

#32116: Fix tor-browser's .mozconfig so that ./mach configure succeeds on Linux 
by
default
--+--
 Reporter:  pospeselr |  Owner:  pospeselr
 Type:  defect| Status:  needs_review
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  TorBrowserTeam201912R |  Actual Points:  0
Parent ID:| Points:  0
 Reviewer:  gk|Sponsor:
--+--
Changes (by pospeselr):

 * keywords:  TorBrowserTeam201912 => TorBrowserTeam201912R
 * status:  needs_revision => needs_review


Comment:

 Ok, squashed the two commits, made them a fixup to
 {{{92f76f10b3ea621c8b1f8ede0837d28ea0e460dc}}}, and force pushed them to
 bug_32116_v2

 tor-browser: https://gitweb.torproject.org/user/richard/tor-
 browser.git/commit/?h=bug_32116_v2=cb3038cf717f25e759fb3fdc0a8e941dbfc4e0f1

--
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] #32672 [Core Tor/Tor]: Reject 0.2.9 and 0.4.0 in dirserv_rejects_tor_version()

[Tor Bug Tracker & Wiki]

#32672: Reject 0.2.9 and 0.4.0 in dirserv_rejects_tor_version()
-+-
 Reporter:  teor |  Owner:  neel
 Type:  task | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  043-should, 041-backport,|  Actual Points:
  042-backport, consider-backport-after- |
  authority-test, fast-fix, network-health   |
Parent ID:   | Points:  0.5
 Reviewer:  teor |Sponsor:
-+-
Changes (by teor):

 * status:  needs_information => needs_revision


Comment:

 I think it is a good idea to exclude 9 relays, so we avoid any bugs in
 unstable 0.4.1 on the network.

 Neel, please also reject 0.4.1.0-alpha-dev to 0.4.1.4-rc.

--
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] #28804 [Core Tor/Tor]: Add circuit padding to padding-spec.txt and write a doc for researchers

[Tor Bug Tracker & Wiki]

#28804: Add circuit padding to padding-spec.txt and write a doc for researchers
-+-
 Reporter:  asn  |  Owner:
 |  mikeperry
 Type:  defect   | Status:
 |  needs_review
 Priority:  High |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  wtf-pad, tor-relay, tor-cell,|  Actual Points:
  padding, tor-spec, 041-proposed, network-  |
  team-roadmap-august, scalability-roadmap   |
Parent ID:   | Points:  2
 Reviewer:  asn  |Sponsor:
 |  Sponsor2
-+-
Changes (by mikeperry):

 * status:  assigned => needs_review


Comment:

 Ok I think this is finally ready. I just squashed down everything into one
 commit for both the dev doc and the quickstart guide.

 This is a doc-only commit. It only needs to be merged into master (though
 we do need it soon so we can link to it in the website oracle blog post).

 https://github.com/torproject/tor/pull/1591

--
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] #32626 [Core Tor/Tor]: Remove extra space in #define in ed25519-donna-portable-identify.h

[Tor Bug Tracker & Wiki]

#32626: Remove extra space in #define in ed25519-donna-portable-identify.h
--+-
 Reporter:  neel  |  Owner:  neel
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:  wontfix
 Keywords:  easy  |  Actual Points:
Parent ID:| Points:
 Reviewer:  ahf   |Sponsor:
--+-

Comment (by teor):

 We will document this policy in #32661.

--
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] #32708 [Core Tor/Tor]: manpage: alphabetize General Options

[Tor Bug Tracker & Wiki]

#32708: manpage: alphabetize General Options
-+-
 Reporter:  catalyst |  Owner:
 |  catalyst
 Type:  task | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  documentation tor-client manpage |  Actual Points:
  easy gsod  |
Parent ID:  #4310| Points:  1
 Reviewer:  teor |Sponsor:
-+-
Changes (by catalyst):

 * cc: teor (added)
 * reviewer:   => teor


Comment:

 Assigning review to teor, because they looked at a previous iteration in
 #4310. teor, please let me know if you'd rather someone else looked at 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] #15701 [Core Tor/Stem]: Use 'GETINFO status/fresh-relay-descs' in tests

[Tor Bug Tracker & Wiki]

#15701: Use 'GETINFO status/fresh-relay-descs' in tests
---+
 Reporter:  atagar |  Owner:  atagar
 Type:  enhancement| Status:  new
 Priority:  Medium |  Milestone:
Component:  Core Tor/Stem  |Version:
 Severity:  Normal | Resolution:
 Keywords:  testing easy   |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+

Comment (by hannelores):

 Hi atagar, would this work?
 https://github.com/torproject/stem/pull/26

--
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] #28531 [Community/Outreach]: Publish a snapshot of what PTs are needed for successful Tor use in each country

[Tor Bug Tracker & Wiki]

#28531: Publish a snapshot of what PTs are needed for successful Tor use in each
country
-+-
 Reporter:  arma |  Owner:  phw
 Type:  task | Status:
 |  assigned
 Priority:  Medium   |  Milestone:
Component:  Community/Outreach   |Version:
 Severity:  Normal   | Resolution:
 Keywords:  censorship, anti-censorship- |  Actual Points:
  roadmap-october, s30-o22a2, s30-o23a2, ux- |
  team   |
Parent ID:  #31279   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor30-must
-+-

Comment (by phw):

 The Briar project [https://grobox.de/tor/bridges.html published a
 snapshot] of the reachability of bridges, default bridges, and directory
 authorities. The data may be outdated by now but it's still something
 worth incorporating in our snapshot. Cecylia
 [https://lists.torproject.org/pipermail/tor-dev/2019-February/013708.html
 posted a summary] of her call with Briar, including the context around
 their snapshot.

--
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] #32708 [Core Tor/Tor]: manpage: alphabetize General Options

[Tor Bug Tracker & Wiki]

#32708: manpage: alphabetize General Options
-+-
 Reporter:  catalyst |  Owner:
 |  catalyst
 Type:  task | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  documentation tor-client manpage |  Actual Points:
  easy gsod  |
Parent ID:  #4310| Points:  1
 Reviewer:   |Sponsor:
-+-
Changes (by catalyst):

 * status:  assigned => needs_review


Comment:

 This is based on Swati's earlier pull request in #4310.

 My pull request is at https://github.com/torproject/tor/pull/1590.

 I separated the unrelated changes, and undid the (unintentional)
 indentation changes. It looks good to me, but I would like someone else to
 quickly look it over.

--
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] #24527 [Applications/Tor Launcher]: Inform users in Tor Launcher of which settings are best for them based on their country

[Tor Bug Tracker & Wiki]

#24527: Inform users in Tor Launcher of which settings are best for them based 
on
their country
-+-
 Reporter:  hellais  |  Owner:  brade
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Launcher|Version:
 Severity:  Normal   | Resolution:
 Keywords:  ux-team, s32-o32a2,  |  Actual Points:
  TorBrowserTeam202004   |
Parent ID:  #31283   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor30-can
-+-
Changes (by phw):

 * cc: cohosh (added)


Comment:

 Replying to [comment:12 phw]:
 > This ticket is similar to #28531, in which we're trying to publish a
 snapshot of how one can get Tor to work in different countries. Tor
 Browser could use this snapshot to decide that's best for the user.
 [[br]]
 Following up on this comment: We briefly discussed this ticket during our
 
[https://trac.torproject.org/projects/tor/wiki/org/meetings/2019Stockholm/Notes/S30
 Sponsor 30 kickoff meeting] in Stockholm. In summary, we need 1) a way for
 Tor Browser to figure out where it is (ideally, we want to know the
 client's country and autonomous system number) and 2) data that can tell
 Tor Browser what to do, once it knows where it is.

 To accomplish 2), we could curate a censorship measurement snapshot (see
 #28531) and put it into Tor Browser. This snapshot maps countries and/or
 autonomous system numbers to circumvention methods. For example, the
 snapshot can tell Tor Browser that if a user is in ASN1234 in Egypt, Tor
 Browser requires a bridge from BridgeDB to bootstrap. Equipped with this
 information, Tor Browser can then immediately make a moat request without
 any assistance from the user. This will decrease the friction for users
 because they don't need to figure out what does and does not work in their
 country. As
 [https://trac.torproject.org/projects/tor/ticket/24527?replyto=12#comment:5
 cypherpunks pointed out above], we won't always get it right, so Tor
 Browser should try to be helpful if our circumvention snapshot is
 incorrect.

 Does this sound reasonable? If so, the anti-censorship team can start
 populating this snapshot with whatever we know about censoring countries.

--
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] #31834 [Circumvention]: Make obfs4 Docker image more usable

[Tor Bug Tracker & Wiki]

#31834: Make obfs4 Docker image more usable
---+---
 Reporter:  phw|  Owner:  phw
 Type:  defect | Status:  closed
 Priority:  Medium |  Milestone:
Component:  Circumvention  |Version:
 Severity:  Normal | Resolution:  fixed
 Keywords:  docker, s30-o24a2  |  Actual Points:  1.1
Parent ID:  #31281 | Points:  1
 Reviewer:  cohosh |Sponsor:  Sponsor30-can
---+---

Comment (by phw):

 Replying to [comment:20 thymbahutymba]:
 > I don't want mess everything up but I think that there are still one
 issue. For understand what I mean: "What if you want/need to change your
 ports?" You volume name still remains related with the previous one, so
 once you deploy the first time the container you are not able to change
 your ports for whatever reason.
 [[br]]
 Don't worry, I really appreciate hearing your thoughts on this!

 Hmm, you are right but this may not necessarily be an issue. When a bridge
 changes its port, it's losing all its users because there is no way for a
 user to learn that their bridge is now available at a new port. As a
 result, I think it's fine if a port change involves creating a new data
 directory. Am I missing something?

--
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] #32550 [Circumvention/Obfs4]: Static tor in docker container

[Tor Bug Tracker & Wiki]

#32550: Static tor in docker container
-+---
 Reporter:  thymbahutymba|  Owner:  phw
 Type:  enhancement  | Status:  assigned
 Priority:  Medium   |  Milestone:
Component:  Circumvention/Obfs4  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  docker, s30-o24a2|  Actual Points:
Parent ID:  #31281   | Points:  2
 Reviewer:   |Sponsor:  Sponsor30-can
-+---

Comment (by phw):

 Replying to [comment:3 thymbahutymba]:
 > I was building again all and I saw that I've made two mistake in the
 Makefile. In order to fix it so that you are able to build by yourself
 without any trouble here the fixing.
 > * In {{{tor}}} target remove libseccomp (that is not present at all);
 > * In {{{tor-${TOR_VER i forgot one slash into the url. The correct
 url is: {{{${TOR}/$@.tar.gz}}}.
 > Forgive me about those mistake, I'm really sorry.
 [[br]]
 No worries! With these changes, I managed to build a statically-compiled
 tor binary with your Makefile.

--
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] #32550 [Circumvention/Obfs4]: Static tor in docker container

[Tor Bug Tracker & Wiki]

#32550: Static tor in docker container
-+---
 Reporter:  thymbahutymba|  Owner:  phw
 Type:  enhancement  | Status:  assigned
 Priority:  Medium   |  Milestone:
Component:  Circumvention/Obfs4  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  docker, s30-o24a2|  Actual Points:
Parent ID:  #31281   | Points:  2
 Reviewer:   |Sponsor:  Sponsor30-can
-+---
Changes (by phw):

 * keywords:  docker => docker, s30-o24a2
 * points:   => 2
 * sponsor:   => Sponsor30-can
 * parent:   => #31281


Comment:

 Replying to [comment:2 thymbahutymba]:
 > Replying to [comment:1 phw]:
 > > I like the idea of making our image more lightweight but I worry about
 the additional complexity in the build process. For example, we also need
 to include Tor's GeoIP database because otherwise the bridge won't be
 reporting the country codes of its clients. Debian's tor package depends
 on tor-geoipdb, which takes care of this for us.
 >
 > Actually this problem does not exist because looking at the debian
 geoipdb package [https://packages.debian.org/sid/all/tor-geoipdb/filelist
 tor-geoipdb] the interesting file are {{{/usr/share/tor/geoip*}}}; if we
 look at the result from the tor statically compilation these file are
 already present.
 [[br]]
 Gotcha, that certainly makes things easier.

 Another reservation I have is that this approach requires us to keep track
 of the latest versions of dependencies and their security vulnerabilities,
 which takes time and effort. Every time we're creating a new docker image,
 we need to figure out what the latest version of OpenSSL etc. is. A Debian
 package however takes care of this for us.

--
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] #32705 [Core Tor/Tor]: check-local tries to run test_practracker.sh even if we have no python

[Tor Bug Tracker & Wiki]

#32705: check-local tries to run test_practracker.sh even if we have no python
---+
 Reporter:  nickm  |  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:  Tor: 0.4.3.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  tor-ci jenkins python  |  Actual Points:
Parent ID: | Points:  0.1
 Reviewer: |Sponsor:
---+
Changes (by nickm):

 * keywords:   => tor-ci jenkins python


--
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] #32240 [Core Tor/Tor]: Tor Travis: Make chutney work on Xenial and Bionic images

[Tor Bug Tracker & Wiki]

#32240: Tor Travis: Make chutney work on Xenial and Bionic images
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:
 |  needs_information
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-ci, chutney, 043-should, |  Actual Points:
  029-backport, 035-backport, 040-backport,  |
  041-backport, 042-backport |
Parent ID:   | Points:  1
 Reviewer:   |Sponsor:
-+-

Comment (by nickm):

 IMO the right solution is to change the chutney default to `Sandbox 0` for
 now, and try to debug the sandbox independently.

 The sandbox issue is probably glibc-dependent, and those are hard to track
 down.  If that's what's going on, we shouldn't let CI be broken because of
 it.

 (Long-term, we should revise the sandbox code to depend less on syscall
 details, but that's a bigger project.)

--
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] #32708 [Core Tor/Tor]: manpage: alphabetize General Options

[Tor Bug Tracker & Wiki]

#32708: manpage: alphabetize General Options
-+-
 Reporter:  catalyst |  Owner:
 |  catalyst
 Type:  task | Status:
 |  assigned
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  documentation tor-client manpage |  Actual Points:
  easy gsod  |
Parent ID:  #4310| Points:  1
 Reviewer:   |Sponsor:
-+-
Changes (by catalyst):

 * type:  defect => task


--
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] #32197 [Internal Services/Service - git]: Gitlab throwing 503 when creating a Merge Request from a forked repository

[Tor Bug Tracker & Wiki]

#32197: Gitlab throwing 503 when creating a Merge Request from a forked 
repository
-+
 Reporter:  hiro |  Owner:  tor-gitadm
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service - git  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  gitlab   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+

Comment (by hiro):

 Logging link to a "similar" issues that I intend to check tomorrow before
 giving up on this:

 https://gitlab.com/gitlab-org/gitlab-foss/issues/50691

--
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] #4310 [Core Tor/Tor]: alphabetize torrc options within sections

[Tor Bug Tracker & Wiki]

#4310: alphabetize torrc options within sections
-+-
 Reporter:  arma |  Owner:  (none)
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  documentation tor-client manpage |  Actual Points:
  easy   |
Parent ID:   | Points:  3
 Reviewer:   |Sponsor:
-+-
Changes (by catalyst):

 * status:  needs_revision => new


Comment:

 Moved the General Options alphabetizing work into child ticket #32708. We
 should create other child tickets for alphabetizing other sections.

--
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] #32708 [Core Tor/Tor]: manpage: alphabetize General Options

[Tor Bug Tracker & Wiki]

#32708: manpage: alphabetize General Options
-+-
 Reporter:   |  Owner:  catalyst
  catalyst   |
 Type:  defect   | Status:  assigned
 Priority:  Medium   |  Milestone:  Tor: 0.4.3.x-final
Component:  Core |Version:
  Tor/Tor|   Keywords:  documentation tor-client manpage
 Severity:  Normal   |  easy gsod
Actual Points:   |  Parent ID:  #4310
   Points:  1|   Reviewer:
  Sponsor:   |
-+-
 This ticket is for Swati's alphabetizing change in #4310. Making this a
 child ticket so we can create other child tickets for working on
 alphabetizing the other sections.

--
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] #15618 [Core Tor/Tor]: Tried to establish rendezvous on non-OR circuit with purpose Acting as rendevous (pending)

[Tor Bug Tracker & Wiki]

#15618: Tried to establish rendezvous on non-OR circuit with purpose Acting as
rendevous (pending)
-+-
 Reporter:  asn  |  Owner:  (none)
 Type:  defect   | Status:
 |  assigned
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-hs needs-insight needs-  |  Actual Points:
  diagnosis  |
Parent ID:   | Points:  1
 Reviewer:   |Sponsor:
-+-

Comment (by arma):

 There have been several reports of this warning popping back up, over the
 past couple days. I increasingly assume it's somebody else's broken client
 implementation.

--
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] #32707 [Core Tor/Tor]: need a mechanism to automatically detect the ipv6 address of the node

[Tor Bug Tracker & Wiki]

#32707: need a mechanism to automatically detect the ipv6 address of the node
--+--
 Reporter:  babut |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Low   |  Component:  Core Tor/Tor
  Version:  Tor: unspecified  |   Severity:  Normal
 Keywords:  ipv6  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
 because for a dynamic ipv6 address specifying the current ipv6 address
 requires automatic editing torrc by a scripts(or have i found no other
 way). it is also necessary to automatically detect when the ipv6 address
 changes as it is done for ipv4

--
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] #32197 [Internal Services/Service - git]: Gitlab throwing 503 when creating a Merge Request from a forked repository

[Tor Bug Tracker & Wiki]

#32197: Gitlab throwing 503 when creating a Merge Request from a forked 
repository
-+
 Reporter:  hiro |  Owner:  tor-gitadm
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service - git  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  gitlab   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+

Comment (by hiro):

 Me and ahf have tried debugging this for quite a while now without luck
 and we are running out of ideas.

 I have been able to isolate what I believe is the line throwing the error:
 https://gitlab.com/gitlab-org/gitlab-
 foss/blob/master/lib/gitlab/git/repository.rb#L744

 The thrown error suggests a bad status for gitaly?
 https://gitlab.com/gitlab-org/gitlab-
 foss/blob/master/lib/gitlab/git/wraps_gitaly_errors.rb#L12

 I am not sure if it has to do with our current setup:
 https://gitweb.torproject.org/admin/services/gitlab/dip.git/tree/

 Maybe we should stop debugging this and just maintain a setup with the
 omnibus debian package.

--
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] #32499 [Circumvention/Snowflake]: Add a build step / documentation for code reuse in Cupcake

[Tor Bug Tracker & Wiki]

#32499: Add a build step / documentation for code reuse in Cupcake
-+-
 Reporter:  arlolra  |  Owner:  arlolra
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Circumvention/Snowflake  |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  snowflake-webextension   |  Actual Points:
Parent ID:   | Points:
 Reviewer:  cohosh   |Sponsor:
-+-
Changes (by arlolra):

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


Comment:

 Merged as, https://gitweb.torproject.org/pluggable-
 transports/snowflake.git/commit/?id=1e45d48a3c4ef05434916d963f0c00d8c0246ac9

--
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] #32197 [Internal Services/Service - git]: Gitlab throwing 503 when creating a Merge Request from a forked repository

[Tor Bug Tracker & Wiki]

#32197: Gitlab throwing 503 when creating a Merge Request from a forked 
repository
-+
 Reporter:  hiro |  Owner:  tor-gitadm
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service - git  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  gitlab   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+
Changes (by gaba):

 * cc: gaba (added)
 * keywords:   => gitlab


--
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] #31909 [Core Tor/Stem]: Write a stem test to detect #31495 regression

[Tor Bug Tracker & Wiki]

#31909: Write a stem test to detect #31495 regression
---+
 Reporter:  nickm  |  Owner:  nickm
 Type:  defect | Status:  closed
 Priority:  Medium |  Milestone:  Tor: 0.4.2.x-final
Component:  Core Tor/Stem  |Version:
 Severity:  Normal | Resolution:  fixed
 Keywords:  042-should |  Actual Points:
Parent ID: | Points:
 Reviewer:  atagar |Sponsor:  Sponsor31-can
---+
Changes (by atagar):

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


Comment:

 "Couple weeks" I said? Damn me, sorry about that. Finally merged.

--
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] #32706 [Core Tor/Tor]: Tried to establish rendezvous on non-OR or non-edge circuit

[Tor Bug Tracker & Wiki]

#32706: Tried to establish rendezvous on non-OR or non-edge circuit
+
 Reporter:  computer_freak  |  Owner:  (none)
 Type:  defect  | Status:  new
 Priority:  Medium  |  Milestone:
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+

Comment (by computer_freak):

 I just see that the ticket #12997 is not exactly the same error message
 than the one i get.
 Seems Google trapped me into it:)
 So if possible please rename this ticket.

 Anyway i get the error message i provided and dont know what to do with
 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] #32499 [Circumvention/Snowflake]: Add a build step / documentation for code reuse in Cupcake

[Tor Bug Tracker & Wiki]

#32499: Add a build step / documentation for code reuse in Cupcake
-+-
 Reporter:  arlolra  |  Owner:  arlolra
 Type:  defect   | Status:  merge_ready
 Priority:  Medium   |  Milestone:
Component:  Circumvention/Snowflake  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  snowflake-webextension   |  Actual Points:
Parent ID:   | Points:
 Reviewer:  cohosh   |Sponsor:
-+-
Changes (by cohosh):

 * status:  needs_review => merge_ready


Comment:

 Looks good, 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] #30368 [Circumvention/Snowflake]: Run some tests to check reachability of snowflake proxies

[Tor Bug Tracker & Wiki]

#30368: Run some tests to check reachability of snowflake proxies
-+---
 Reporter:  cohosh   |  Owner:  cohosh
 Type:  task | Status:  needs_review
 Priority:  Medium   |  Milestone:
Component:  Circumvention/Snowflake  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  anti-censorship-roadmap  |  Actual Points:
Parent ID:   | Points:
 Reviewer:  phw  |Sponsor:  Sponsor28-can
-+---

Comment (by cohosh):

 The code currently lives here: https://github.com/cohosh/bridgetest

--
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] #30368 [Circumvention/Snowflake]: Run some tests to check reachability of snowflake proxies

[Tor Bug Tracker & Wiki]

#30368: Run some tests to check reachability of snowflake proxies
-+---
 Reporter:  cohosh   |  Owner:  cohosh
 Type:  task | Status:  needs_review
 Priority:  Medium   |  Milestone:
Component:  Circumvention/Snowflake  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  anti-censorship-roadmap  |  Actual Points:
Parent ID:   | Points:
 Reviewer:  phw  |Sponsor:  Sponsor28-can
-+---
Changes (by cohosh):

 * status:  accepted => needs_review
 * reviewer:   => phw


Comment:

 I've made some recent changes to the reachability scripts for #32657. I'll
 keep this ticket for a review of the correctness of those scripts and
 whether there are other tests that would be useful for us here.

--
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] #31085 [Circumvention/Snowflake]: Publish the Snowflake WebExtension on AMO for Android

[Tor Bug Tracker & Wiki]

#31085: Publish the Snowflake WebExtension on AMO for Android
+
 Reporter:  cypherpunks |  Owner:  (none)
 Type:  defect  | Status:  new
 Priority:  Medium  |  Milestone:
Component:  Circumvention/Snowflake |Version:
 Severity:  Normal  | Resolution:
 Keywords:  snowflake-webextension android  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+

Comment (by cohosh):

 arma just brought up a question in IRC about whether this problem is due
 to android or due to Firefox on android, and whether we can get proxies to
 work in a mobile setting if we use something other than Firefox to run the
 proxy 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] #32657 [Circumvention/Snowflake]: Investigate Snowflake blocking in China

[Tor Bug Tracker & Wiki]

#32657: Investigate Snowflake blocking in China
-+---
 Reporter:  cohosh   |  Owner:  cohosh
 Type:  defect   | Status:  needs_information
 Priority:  High |  Milestone:
Component:  Circumvention/Snowflake  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  blocking, china  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:  Sponsor28
-+---
Changes (by cohosh):

 * status:  assigned => needs_information


Comment:

 Here are the results from some throughput tests I ran from the VPS in
 China on December 6th:

 To summarize the tests, I attempted to bootstrap a Tor connection using
 Snowflake as the pluggable transport 100 times. If the bootstrap was
 successful, I then proceeded to download a 1MB file using `torsocks`. I
 measured the bootstrap progress (i.e., how far the Tor connection
 bootstrap proceeded before the 90 second timeout), and also looked at
 packet captures of UDP traffic to determine where, if at all, the
 Snowflake WebRTC connection failed.

 [[Image(snowflake-tor-bootstrap-china-2019-12-06.png,50%)]]

 Surprisingly, almost all Snowflake connections succeeded this time around,
 with only 4 connections that failed to bootstrap to 100%.

 [[Image(snowflake-webrtc-stages-china-2019-12-06.png,80%)]]

 Looking at the snowflake connection data, only three connections to the
 snowflake provided by the snowflake-broker failed at the phase where the
 client tries to open a data channel to the snowflake.

 The throughput was also better than expected:

 [[Image(snowflake-throughput-china-2019-12-06.png,80%)]]

 The mean throughput was 110 KBps, with a standard deviation of 80 KBps.
 This isn't that much slower than the throughput of 190 KBps reported from
 a VPS in Canada in #32545:comment3. Some slowness is to be expected given
 the geographical distance of this probe site.

 This data contradicts the previous tests above where half of all
 snowflakes are failing. We used the same basic probe test to collect this
 data, which suggests that if censorship is happening, it is not consistent
 yet. I'm going to set up some recurring probes of this type to see if the
 reachability of snowflake changes over the next few days.

--
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] #32636 [Applications/Tor Launcher]: Clean up locales shipped with Tor Launcher

[Tor Bug Tracker & Wiki]

#32636: Clean up locales shipped with Tor Launcher
---+---
 Reporter:  gk |  Owner:  brade
 Type:  task   | Status:  new
 Priority:  Medium |  Milestone:
Component:  Applications/Tor Launcher  |Version:
 Severity:  Normal | Resolution:
 Keywords:  TorBrowserTeam201912   |  Actual Points:
Parent ID: | Points:  0.25
 Reviewer: |Sponsor:
---+---

Comment (by gk):

 Replying to [comment:1 mcs]:
 > I am not sure what should be done for this ticket. The strategy for
 handling translations is different for Tor Launcher compared to Torbutton.

 That's true and is okay. What needs to get done is to adapt the locales to
 the code Mozilla is using as this got done server-side. E.g. we have now
 `sv-SE` we should use and not `sv` anymore. Otherwise the translations
 updating is not working anymore as expected. And while doing that there
 might be scripts we need to adapt. (You might easily see what we need to
 adapt by just fetching the latest translations)

 > For Torbutton, only locales listed in the `BUNDLE_LOCALES` variable
 within `import-translations.sh` are updated from Transifex, and we only
 ship some locales in Tor Browser (presumably, the set of locales listed in
 Torbutton's `jar.mn` file matches the set in `BUNDLE_LOCALES`).
 >
 > For Tor Launcher, the `localization/import_translations` script updates
 from Transifex and keeps the .dtd and .properties files for every locale
 that (1) includes all necessary files and (2) has any translated strings.
 Then a new `jar.mn` file is generated that includes all available locales,
 which causes us to we ship all of the locales in Tor Browser. The original
 reason for not excluding any locales was that that another application
 that uses Tor Launcher might use a locale that we do not use in Tor
 Browser, but I don't think any other application uses our jar.mn file.
 >
 > I have two questions for gk (or anyone):
 > 1. What do you mean by "removing the ones we don't support anymore?"
 Should we compare what is available in the translation.git repo with the
 locales that are in the Tor Launcher repo?

 Yes, and what Mozilla is actually providing. I suspect Tor Launcher is
 coming with more locales than the latter at least (`ru@petr1708`
 seriously? or `zh-CN.GB2312`) and it might make sense to reduce that so it
 matches better what Mozilla is providing as I think we won't be in a
 situation that Tor Launcher is shipped for a locale without a
 corresponding Mozilla one.

 > 2. Should we add a `BUNDLE_LOCALES` variable to Tor Launcher's
 `import_translations` script and use it to determine which locales are
 part of Tor Browser? I think reducing the locale-related lines that are
 added to the generated `jar.mn' file should be enough to reduce the set of
 locales that ship inside the browser. I don't see any harm in continuing
 to update Tor Launcher's locale files for locales that we don't ship,
 unless that creates too much pain when doing release work (updating
 translations).

 I don't have a strong opinion here. Whatever works for you works for me.

--
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] #32657 [Circumvention/Snowflake]: Investigate Snowflake blocking in China

[Tor Bug Tracker & Wiki]

#32657: Investigate Snowflake blocking in China
-+---
 Reporter:  cohosh   |  Owner:  cohosh
 Type:  defect   | Status:  assigned
 Priority:  High |  Milestone:
Component:  Circumvention/Snowflake  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  blocking, china  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:  Sponsor28
-+---
Changes (by cohosh):

 * Attachment "snowflake-throughput-china-2019-12-06.png" 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] #32657 [Circumvention/Snowflake]: Investigate Snowflake blocking in China

[Tor Bug Tracker & Wiki]

#32657: Investigate Snowflake blocking in China
-+---
 Reporter:  cohosh   |  Owner:  cohosh
 Type:  defect   | Status:  assigned
 Priority:  High |  Milestone:
Component:  Circumvention/Snowflake  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  blocking, china  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:  Sponsor28
-+---
Changes (by cohosh):

 * Attachment "snowflake-webrtc-stages-china-2019-12-06.png" 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] #32657 [Circumvention/Snowflake]: Investigate Snowflake blocking in China

[Tor Bug Tracker & Wiki]

#32657: Investigate Snowflake blocking in China
-+---
 Reporter:  cohosh   |  Owner:  cohosh
 Type:  defect   | Status:  assigned
 Priority:  High |  Milestone:
Component:  Circumvention/Snowflake  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  blocking, china  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:  Sponsor28
-+---
Changes (by cohosh):

 * Attachment "snowflake-tor-bootstrap-china-2019-12-06.png" 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] #32657 [Circumvention/Snowflake]: Investigate Snowflake blocking in China

[Tor Bug Tracker & Wiki]

#32657: Investigate Snowflake blocking in China
-+---
 Reporter:  cohosh   |  Owner:  cohosh
 Type:  defect   | Status:  assigned
 Priority:  High |  Milestone:
Component:  Circumvention/Snowflake  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  blocking, china  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:  Sponsor28
-+---
Changes (by cohosh):

 * Attachment "snowflake-throughput-china-2019-12-16.png" 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] #30334 [Applications/Tor Browser]: build_go_lib for executables?

[Tor Bug Tracker & Wiki]

#30334: build_go_lib for executables?
+--
 Reporter:  JeremyRand  |  Owner:  boklm
 Type:  enhancement | Status:  needs_review
 Priority:  Medium  |  Milestone:
Component:  Applications/Tor Browser|Version:
 Severity:  Normal  | Resolution:
 Keywords:  tbb-rbm, TorBrowserTeam201912R  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  boklm   |Sponsor:
+--

Comment (by boklm):

 I rebased the patch on master in branch `bug_30334_v2`:
 https://gitweb.torproject.org/user/boklm/tor-browser-
 build.git/commit/?h=bug_30334_v2=debe3ddd8e3967d4b56632a9b11b7cde14e01f16

 I had to adapt the changes from #28803 in `projects/obfs4/build` to do
 them in `projects/obfs4/config`.

 JeremyRand: Could you check whether the patch still looks good for you?

--
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] #30237 [Applications/Tor Browser]: Tor Browser: Improve TBB UI of hidden service client authorization

[Tor Bug Tracker & Wiki]

#30237: Tor Browser: Improve TBB UI of hidden service client authorization
-+-
 Reporter:  asn  |  Owner:  mcs
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  network-team-roadmap-september,  |  Actual Points:
  TorBrowserTeam201912R  |
Parent ID:  #3   | Points:
 Reviewer:  pospeselr, sysrqb|Sponsor:
 |  Sponsor27-must
-+-

Comment (by antonela):

 Replying to [comment:46 mcs]:
 > Replying to [comment:45 antonela]:
 > > #32562 is done. Will we include it in the UI? What is needed on my
 side?
 >
 > Yes, we plan to add a simple checkbox below the key input field. We need
 to agree on the label; probably something like `Remember this key`. What
 do you think?

 Works for me. 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] #32704 [Core Tor/Tor]: Port changelog tools to python 3

[Tor Bug Tracker & Wiki]

#32704: Port changelog tools to python 3
--+
 Reporter:  nickm |  Owner:  nickm
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:  Tor: 0.4.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:|  Actual Points:  0
Parent ID:| Points:  0
 Reviewer:|Sponsor:
--+
Changes (by nickm):

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


Comment:

 CI passed; merging.

--
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] #32657 [Circumvention/Snowflake]: Investigate Snowflake blocking in China

[Tor Bug Tracker & Wiki]

#32657: Investigate Snowflake blocking in China
-+---
 Reporter:  cohosh   |  Owner:  cohosh
 Type:  defect   | Status:  assigned
 Priority:  High |  Milestone:
Component:  Circumvention/Snowflake  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  blocking, china  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:  Sponsor28
-+---
Changes (by cohosh):

 * Attachment "snowflake-webrtc-stages-china-2019-12-06.pdf" 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] #32657 [Circumvention/Snowflake]: Investigate Snowflake blocking in China

[Tor Bug Tracker & Wiki]

#32657: Investigate Snowflake blocking in China
-+---
 Reporter:  cohosh   |  Owner:  cohosh
 Type:  defect   | Status:  assigned
 Priority:  High |  Milestone:
Component:  Circumvention/Snowflake  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  blocking, china  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:  Sponsor28
-+---
Changes (by cohosh):

 * Attachment "snowflake-tor-bootstrap-china-2019-12-06.pdf" 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] #32657 [Circumvention/Snowflake]: Investigate Snowflake blocking in China

[Tor Bug Tracker & Wiki]

#32657: Investigate Snowflake blocking in China
-+---
 Reporter:  cohosh   |  Owner:  cohosh
 Type:  defect   | Status:  assigned
 Priority:  High |  Milestone:
Component:  Circumvention/Snowflake  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  blocking, china  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:  Sponsor28
-+---
Changes (by cohosh):

 * Attachment "snowflake-throughput-china-2019-12-16.pdf" 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

[tor-bugs] #32706 [Core Tor/Tor]: Tried to establish rendezvous on non-OR or non-edge circuit

[Tor Bug Tracker & Wiki]

#32706: Tried to establish rendezvous on non-OR or non-edge circuit
+--
 Reporter:  computer_freak  |  Owner:  (none)
 Type:  defect  | Status:  new
 Priority:  Medium  |  Component:  Core Tor/Tor
  Version:  |   Severity:  Normal
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
 In #12997comment:6 nickm requested to open a new ticket if someone gets
 that warning again.

 I get that warning since weeks on 0.4.1.6 about once a day on different
 relays.
 Even if #12997 is implemented i never saw a more specific warning than
 that simple line.

 This is all the log shows me:

 {{{
 Dec 09 10:36:03.000 [notice] DoS mitigation since startup: 10 circuits
 killed with too many cells. 1835037 circuits rejected, 91 marked
 addresses. 711976 connections closed. 10660 single hop clients refused.
 Dec 09 12:29:48.000 [warn] Tried to establish rendezvous on non-edge
 circuit
 Dec 09 16:36:03.000 [notice] Heartbeat: Tor's uptime is 47 days 0:00
 hours, with 23309 circuits open. I've sent 56816.96 GB and received
 56583.09 GB.
 }}}

--
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] #31878 [Circumvention/BridgeDB]: Look into making BridgeDB more resilient

[Tor Bug Tracker & Wiki]

#31878: Look into making BridgeDB more resilient
+
 Reporter:  phw |  Owner:  (none)
 Type:  task| Status:  new
 Priority:  Medium  |  Milestone:
Component:  Circumvention/BridgeDB  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  s30-o24a5   |  Actual Points:
Parent ID:  #31281  | Points:  10
 Reviewer:  |Sponsor:  Sponsor30-must
+
Changes (by cohosh):

 * cc: gman999, 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] #31878 [Circumvention/BridgeDB]: Make BridgeDB and bridge authority more resilient

[Tor Bug Tracker & Wiki]

#31878: Make BridgeDB and bridge authority more resilient
+
 Reporter:  phw |  Owner:  (none)
 Type:  task| Status:  new
 Priority:  Medium  |  Milestone:
Component:  Circumvention/BridgeDB  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  s30-o24a5   |  Actual Points:
Parent ID:  #31281  | Points:  10
 Reviewer:  |Sponsor:  Sponsor30-must
+
Changes (by phw):

 * cc: gman999, 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] #31878 [Circumvention/BridgeDB]: Make BridgeDB and bridge authority more resilient (was: Look into making BridgeDB more resilient)

[Tor Bug Tracker & Wiki]

#31878: Make BridgeDB and bridge authority more resilient
+
 Reporter:  phw |  Owner:  (none)
 Type:  task| Status:  new
 Priority:  Medium  |  Milestone:
Component:  Circumvention/BridgeDB  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  s30-o24a5   |  Actual Points:
Parent ID:  #31281  | Points:  10
 Reviewer:  |Sponsor:  Sponsor30-must
+
Changes (by phw):

 * cc: gman999, cohosh (removed)


Comment:

 gman999 thought about setting up two bridge authorities behind a single,
 virtual IP address. This will make our bridge authority more resistant to
 hardware failure because if one goes down, there's still the other one
 that continues operations.

 Once set up, both bridge authorities would then separately sync their
 bridge descriptors to BridgeDB, which  expects a single directory of
 bridge descriptors, so we will either have to 1) teach BridgeDB (and Tor
 Metrics) how to handle >1 directory of bridge descriptors, or 2) write a
 tool that takes as input an arbitrary number of directories containing
 bridge descriptors and then produce as output a combined "view" of these
 descriptors. We agreed to first take a look at a tool that can combine
 "views" because it would simplify our processing pipeline and it may be
 easy to do with Stem.

--
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] #31878 [Circumvention/BridgeDB]: Look into making BridgeDB more resilient

[Tor Bug Tracker & Wiki]

#31878: Look into making BridgeDB more resilient
+
 Reporter:  phw |  Owner:  (none)
 Type:  task| Status:  new
 Priority:  Medium  |  Milestone:
Component:  Circumvention/BridgeDB  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  s30-o24a5   |  Actual Points:
Parent ID:  #31281  | Points:  10
 Reviewer:  |Sponsor:  Sponsor30-must
+

Comment (by gman999):

 gman999 into the cc

--
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] #32460 [Webpages/Website]: download page has confusing flow, especially with donate banner

[Tor Bug Tracker & Wiki]

#32460: download page has confusing flow, especially with donate banner
--+--
 Reporter:  arma  |  Owner:  hiro
 Type:  defect| Status:  new
 Priority:  High  |  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ux-team   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by core):

 Antonela, I would suggest the download page either not having the banner
 or scrolling to the downloads part. Because an issue arises on computers
 with low screen resolution where they only see a bit of the purple part
 and when they click on "Download Tor Browser" the user doesn't notice that
 the page actually changed

--
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] #32636 [Applications/Tor Launcher]: Clean up locales shipped with Tor Launcher

[Tor Bug Tracker & Wiki]

#32636: Clean up locales shipped with Tor Launcher
---+---
 Reporter:  gk |  Owner:  brade
 Type:  task   | Status:  new
 Priority:  Medium |  Milestone:
Component:  Applications/Tor Launcher  |Version:
 Severity:  Normal | Resolution:
 Keywords:  TorBrowserTeam201912   |  Actual Points:
Parent ID: | Points:  0.25
 Reviewer: |Sponsor:
---+---
Changes (by mcs):

 * cc: tbb-team (added)


Comment:

 I am not sure what should be done for this ticket. The strategy for
 handling translations is different for Tor Launcher compared to Torbutton.

 For Torbutton, only locales listed in the `BUNDLE_LOCALES` variable within
 `import-translations.sh` are updated from Transifex, and we only ship some
 locales in Tor Browser (presumably, the set of locales listed in
 Torbutton's `jar.mn` file matches the set in `BUNDLE_LOCALES`).

 For Tor Launcher, the `localization/import_translations` script updates
 from Transifex and keeps the .dtd and .properties files for every locale
 that (1) includes all necessary files and (2) has any translated strings.
 Then a new `jar.mn` file is generated that includes all available locales,
 which causes us to we ship all of the locales in Tor Browser. The original
 reason for not excluding any locales was that that another application
 that uses Tor Launcher might use a locale that we do not use in Tor
 Browser, but I don't think any other application uses our jar.mn file.

 I have two questions for gk (or anyone):
 1. What do you mean by "removing the ones we don't support anymore?"
 Should we compare what is available in the translation.git repo with the
 locales that are in the Tor Launcher repo?
 2. Should we add a `BUNDLE_LOCALES` variable to Tor Launcher's
 `import_translations` script and use it to determine which locales are
 part of Tor Browser? I think reducing the locale-related lines that are
 added to the generated `jar.mn' file should be enough to reduce the set of
 locales that ship inside the browser. I don't see any harm in continuing
 to update Tor Launcher's locale files for locales that we don't ship,
 unless that creates too much pain when doing release work (updating
 translations).

--
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] #4310 [Core Tor/Tor]: alphabetize torrc options within sections

[Tor Bug Tracker & Wiki]

#4310: alphabetize torrc options within sections
-+-
 Reporter:  arma |  Owner:  (none)
 Type:  task | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  documentation tor-client manpage |  Actual Points:
  easy   |
Parent ID:   | Points:  3
 Reviewer:   |Sponsor:
-+-

Comment (by swati):

 I am sorry. My intention was to only re-rder man page entries. I didn't
 realize how in the process of copying and pasting, the whitespace changes
 emerged. I'll try to figure out how this happened. Should I close the PR
 and submit this again?

 Replying to [comment:12 teor]:
 > Hi swati,
 >
 > Replying to [comment:5 nickm]:
 > > If you want to submit a patch, please make sure that it does
 '''nothing else''' besides reorder the manpage entries; otherwise, it will
 be hard to review.
 >
 > This patch re-orders manpage entries, but it also makes whitespace
 changes, for example:
 > https://github.com/torproject/tor/pull/1567/files#diff-
 53a84e5af0d074614e6d722a25038cb7R277
 >
 > Some of these whitespace changes appear to be incorrect:
 > https://github.com/torproject/tor/pull/1567/files#diff-
 53a84e5af0d074614e6d722a25038cb7R283
 >
 > Please make a pull request that only re-orders manpage option entries,
 and doesn't make any other changes.
 >
 > If you are using git, all the changes should be highlighted as "moved"
 with `git diff --color-moved`.

--
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] #32705 [Core Tor/Tor]: check-local tries to run test_practracker.sh even if we have no python

[Tor Bug Tracker & Wiki]

#32705: check-local tries to run test_practracker.sh even if we have no python
--+
 Reporter:  nickm |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.4.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:  0.1   |   Reviewer:
  Sponsor:|
--+
 It looks like we have a failure on Jenkins:
 https://jenkins.torproject.org/job/tor-ci-linux-
 master/ARCHITECTURE=amd64,SUITE=bullseye/4402/consoleFull

 It seems like when we `check-practracker-unit-tests`, we try to run it
 even when we don't have python installed.  Additionally, we don't set the
 PYTHON environment variable when we run `check-pracktracker-unit-tests`,
 so the script can look for python with the wrong name.

 Both of these problems are solved if we remove `check-practracker-unit-
 tests`, I believe, since test_practracker.sh is already listed in
 TESTSCRIPTS, so we don't acutally need to have it in check-local as we
 thought in #32609

--
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] #32119 [Applications/Tor Browser]: onboarding for "Goodbye Onion Button" could be better

[Tor Bug Tracker & Wiki]

#32119: onboarding for "Goodbye Onion Button" could be better
-+-
 Reporter:  catalyst |  Owner:  brade
 Type:  defect   | Status:
 |  needs_information
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ux-team, tbb-onboarding, |  Actual Points:
  tbb-9.0-issues, tbb-9.1.0-can, |
  TorBrowserTeam201912   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by mcs):

 * status:  assigned => needs_information


Comment:

 Two questions:
 * Is the UX team happy with the new design?
 * Is it worth expending the engineering and localization effort that is
 required to make these changes? I assume most Tor Browser users have
 already updated to 9.x and they probably already looked at the
 onboarding... which means they will never see this new approach. In other
 words, it seems like we missed our opportunity to teach our users about
 this change.

--
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] #32090 [Internal Services/Tor Sysadmin Team]: Blog status and where to go

[Tor Bug Tracker & Wiki]

#32090: Blog status and where to go
-+-
 Reporter:  hiro |  Owner:  tpa
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by anarcat):

 * Attachment "snap-2019.12.09-11.30.12.png" 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] #32090 [Internal Services/Tor Sysadmin Team]: Blog status and where to go

[Tor Bug Tracker & Wiki]

#32090: Blog status and where to go
-+-
 Reporter:  hiro |  Owner:  tpa
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by anarcat):

 * Attachment "snap-2019.12.09-11.28.37.png" 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] #32239 [Internal Services/Service - cache]: setup a cache frontend for the blog

[Tor Bug Tracker & Wiki]

#32239: setup a cache frontend for the blog
---+-
 Reporter:  anarcat|  Owner:  anarcat
 Type:  task   | Status:  closed
 Priority:  Medium |  Milestone:
Component:  Internal Services/Service - cache  |Version:
 Severity:  Normal | Resolution:  fixed
 Keywords: |  Actual Points:
Parent ID:  #32090 | Points:
 Reviewer: |Sponsor:
---+-
Changes (by anarcat):

 * Attachment "snap-2019.12.09-11.30.12.png" 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] #32239 [Internal Services/Service - cache]: setup a cache frontend for the blog

[Tor Bug Tracker & Wiki]

#32239: setup a cache frontend for the blog
---+-
 Reporter:  anarcat|  Owner:  anarcat
 Type:  task   | Status:  closed
 Priority:  Medium |  Milestone:
Component:  Internal Services/Service - cache  |Version:
 Severity:  Normal | Resolution:  fixed
 Keywords: |  Actual Points:
Parent ID:  #32090 | Points:
 Reviewer: |Sponsor:
---+-
Changes (by anarcat):

 * Attachment "snap-2019.12.09-11.28.37.png" 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] #30984 [Core Tor/Tor]: Make a key-value line abstraction to output control replies

[Tor Bug Tracker & Wiki]

#30984: Make a key-value line abstraction to output control replies
-+-
 Reporter:  catalyst |  Owner:
 |  catalyst
 Type:  defect   | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  042-deferred-20190918, early-review  |  Actual Points:  8
Parent ID:  #29210   | Points:  5
 Reviewer:  teor |Sponsor:
 |  Sponsor31-can
-+-
Changes (by catalyst):

 * actualpoints:   => 8


Comment:

 Replying to [comment:15 teor]:
 > Looks good to me, but we can't merge until after the pending releases.
 >
 > Also, please remember to fill in actual points!
 Thanks! I fixed the whitespace issue you commented on in the pull request.

--
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] #32704 [Core Tor/Tor]: Port changelog tools to python 3

[Tor Bug Tracker & Wiki]

#32704: Port changelog tools to python 3
--+
 Reporter:  nickm |  Owner:  nickm
 Type:  defect| Status:  merge_ready
 Priority:  Medium|  Milestone:  Tor: 0.4.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:  0
Parent ID:| Points:  0
 Reviewer:|Sponsor:
--+

Comment (by nickm):

 oops, PR is https://github.com/torproject/tor/pull/1589 . Going to let CI
 pass before merging.

--
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] #32460 [Webpages/Website]: download page has confusing flow, especially with donate banner

[Tor Bug Tracker & Wiki]

#32460: download page has confusing flow, especially with donate banner
--+--
 Reporter:  arma  |  Owner:  hiro
 Type:  defect| Status:  new
 Priority:  High  |  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ux-team   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by mcs):

 Please replace "apple" with "macOS", i.e., `Download for macOS`.

--
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] #32460 [Webpages/Website]: download page has confusing flow, especially with donate banner

[Tor Bug Tracker & Wiki]

#32460: download page has confusing flow, especially with donate banner
--+--
 Reporter:  arma  |  Owner:  hiro
 Type:  defect| Status:  new
 Priority:  High  |  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ux-team   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by antonela):

 Based on last week's discussion, I've pushed these changes to staging.

 
https://dip.torproject.org/torproject/web/tpo/commit/4d29cfb29567f5ff3eea78992e6068f5fc24801a

 We still have a to-do pending. This is a WIP

 https://lektor-staging.torproject.org/tpo/staging/download/

--
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] #32704 [Core Tor/Tor]: Port changelog tools to python 3

[Tor Bug Tracker & Wiki]

#32704: Port changelog tools to python 3
--+
 Reporter:  nickm |  Owner:  nickm
 Type:  defect| Status:  merge_ready
 Priority:  Medium|  Milestone:  Tor: 0.4.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:  0
Parent ID:| Points:  0
 Reviewer:|Sponsor:
--+
Changes (by ahf):

 * status:  needs_review => merge_ready


Comment:

 Looks fine, but it's not a PR in the link, so I could not check CI, but it
 looks like a minor change that doesn't impact any of the CI checks?

--
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] #29210 [Core Tor/Tor]: Distribute control.c functionality across various modules

[Tor Bug Tracker & Wiki]

#29210: Distribute control.c functionality across various modules
-+-
 Reporter:  nickm|  Owner:
 |  catalyst
 Type:  task | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  network-team-roadmap-september,  |  Actual Points:
  042-deferred-20190918  |
Parent ID:   | Points:  23
 Reviewer:   |Sponsor:
 |  Sponsor31-can
-+-
Changes (by catalyst):

 * status:  new => merge_ready


Comment:

 Remaining child ticket is merge_ready.

--
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] #32674 [Applications/Tor Browser]: Change link on 'Get involved' in about:tor to new community portal

[Tor Bug Tracker & Wiki]

#32674: Change link on 'Get involved' in about:tor to new community portal
-+-
 Reporter:  emmapeel |  Owner:  tbb-team
 Type:  defect   | Status:
 |  needs_information
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  community, TorBrowserTeam201912  |  Actual Points:
Parent ID:   | Points:  0.1
 Reviewer:   |Sponsor:
-+-
Changes (by mcs):

 * status:  new => needs_information


Comment:

 emmapeel, should the link be simply https://community.torproject.org/ ?

--
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] #32704 [Core Tor/Tor]: Port changelog tools to python 3

[Tor Bug Tracker & Wiki]

#32704: Port changelog tools to python 3
--+
 Reporter:  nickm |  Owner:  nickm
 Type:  defect| Status:  needs_review
 Priority:  Medium|  Milestone:  Tor: 0.4.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:  0
Parent ID:| Points:  0
 Reviewer:|Sponsor:
--+
Changes (by nickm):

 * status:  accepted => needs_review


--
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] #32624 [Applications/Tor Browser]: localStorage is not shared between tabs

[Tor Bug Tracker & Wiki]

#32624: localStorage is not shared between tabs
--+--
 Reporter:  nDe15o|  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ff78-esr-will-have|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by Thorin):

 Replying to [comment:4 Thorin]:
 > The thing is next_gen was not flipped on until FF70, and then they
 flipped it back in 70.0.1 due to issues that AFAIK shouldn't affect TB
 since it doesn't have persistent data.
 >
 > I don't think LSNG = true would necessarily be ready for ESR68, but
 might be perfectly fine given TB's setup (PB mode etc). I'll ping Johann

 OK, so Johann has replied, and said "I don't think I have any input on
 [this tor] ticket, let me know if you need me to forward it to folks who
 are actually working on LSNG

 So I'll leave it up to you guys if we just wait until the next ESR, or if
 you want me to ask Johann to ask the right folks to let us know if it's OK
 to flip in Tor Browser

--
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] #32704 [Core Tor/Tor]: Port changelog tools to python 3

[Tor Bug Tracker & Wiki]

#32704: Port changelog tools to python 3
--+
 Reporter:  nickm |  Owner:  nickm
 Type:  defect| Status:  accepted
 Priority:  Medium|  Milestone:  Tor: 0.4.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:  0
Parent ID:| Points:  0
 Reviewer:|Sponsor:
--+
Changes (by nickm):

 * status:  new => accepted
 * owner:  (none) => nickm
 * actualpoints:   => 0


Comment:

 Branch is `ticket32704` with PR at
 https://github.com/nmathewson/tor/pull/new/ticket32704 .

 I've tested these changes by using them with python2 and python3 to
 regenerate the changelogs for the current pending releases.  The output
 looks correct.

--
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] #32704 [Core Tor/Tor]: Port changelog tools to python 3

[Tor Bug Tracker & Wiki]

#32704: Port changelog tools to python 3
--+
 Reporter:  nickm |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.4.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:  0 |   Reviewer:
  Sponsor:|
--+
 I use sortChanges.py and format_changelog.py to prepare changelogs.  These
 scripts don't use use the python3 list syntax. I should port them.

--
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] #32672 [Core Tor/Tor]: Reject 0.2.9 and 0.4.0 in dirserv_rejects_tor_version()

[Tor Bug Tracker & Wiki]

#32672: Reject 0.2.9 and 0.4.0 in dirserv_rejects_tor_version()
-+-
 Reporter:  teor |  Owner:  neel
 Type:  task | Status:
 |  needs_information
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  043-should, 041-backport,|  Actual Points:
  042-backport, consider-backport-after- |
  authority-test, fast-fix, network-health   |
Parent ID:   | Points:  0.5
 Reviewer:  teor |Sponsor:
-+-

Comment (by dgoulet):

 Replying to [comment:11 gk]:
 > It seems like 9 if I understand the output correctly:
 > {{{
 >2: 0.4.1.2-alpha [0.02 %]
 >5: 0.4.1.3-alpha [0.07 %]
 >2: 0.4.1.4-rc[0.00 %]
 > }}}

 Correct. I see the same.

--
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] #32672 [Core Tor/Tor]: Reject 0.2.9 and 0.4.0 in dirserv_rejects_tor_version()

[Tor Bug Tracker & Wiki]

#32672: Reject 0.2.9 and 0.4.0 in dirserv_rejects_tor_version()
-+-
 Reporter:  teor |  Owner:  neel
 Type:  task | Status:
 |  needs_information
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  043-should, 041-backport,|  Actual Points:
  042-backport, consider-backport-after- |
  authority-test, fast-fix, network-health   |
Parent ID:   | Points:  0.5
 Reviewer:  teor |Sponsor:
-+-

Comment (by gk):

 It seems like 9 if I understand the output correctly:
 {{{
2: 0.4.1.2-alpha [0.02 %]
5: 0.4.1.3-alpha [0.07 %]
2: 0.4.1.4-rc[0.00 %]
 }}}

--
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] #32672 [Core Tor/Tor]: Reject 0.2.9 and 0.4.0 in dirserv_rejects_tor_version()

[Tor Bug Tracker & Wiki]

#32672: Reject 0.2.9 and 0.4.0 in dirserv_rejects_tor_version()
-+-
 Reporter:  teor |  Owner:  neel
 Type:  task | Status:
 |  needs_information
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  043-should, 041-backport,|  Actual Points:
  042-backport, consider-backport-after- |
  authority-test, fast-fix, network-health   |
Parent ID:   | Points:  0.5
 Reviewer:  teor |Sponsor:
-+-

Comment (by teor):

 Thanks dgoulet, looks like we need to contact operators on 0.3.4 and
 earlier, and 0.4.0, particularly 0.2.9 and 0.4.0.5.

 There was a typo in my last post, we are actually talking about rejecting
 unstable 0.4.1 versions, as well as all of 0.4.0.

 How many relays are on 0.4.1 unstable?

--
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] #15302 [Applications/Tor Browser]: Tor browser doesn't recognize change of network interface which provides internet

[Tor Bug Tracker & Wiki]

#15302: Tor browser doesn't recognize change of network interface which provides
internet
--+--
 Reporter:  krichter  |  Owner:  tbb-team
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:  user disappeared
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by teor):

 I regularly change network interfaces using Tor Browser, and I don't see
 this issue. Many other people do the same thing.

 If this ticket was moved to Core Tor, we'd just close it anyway, because
 we can't reproduce 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] #32639 [Core Tor/Tor]: cancel_descriptor_fetches() uses wrong connection list function

[Tor Bug Tracker & Wiki]

#32639: cancel_descriptor_fetches() uses wrong connection list function
-+
 Reporter:  asn  |  Owner:  neel
 Type:  defect   | Status:  needs_review
 Priority:  Medium   |  Milestone:  Tor: 0.4.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-hs newnym backport?  |  Actual Points:
Parent ID:   | Points:
 Reviewer:  asn  |Sponsor:  Sponsor27-can
-+
Changes (by asn):

 * reviewer:   => asn


--
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] #32588 [Core Tor/Tor]: Setting ORPort [ipv6]:auto mistakenly advertises port 94

[Tor Bug Tracker & Wiki]

#32588: Setting ORPort [ipv6]:auto mistakenly advertises port 94
---+---
 Reporter:  arma   |  Owner:  neel
 Type:  defect | Status:
   |  needs_information
 Priority:  Medium |  Milestone:  Tor:
   |  0.4.3.x-final
Component:  Core Tor/Tor   |Version:  Tor:
   |  0.4.1.6
 Severity:  Normal | Resolution:
 Keywords:  ipv6, memory-safety, security-low  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---

Comment (by teor):

 It's also worth noting that we're getting 0x5e = 94 in the output, and not
 0xcc5e or 0x5ecc. So it's just a one byte overflow. And it's happening
 some time after the port is opened, but before the relay descriptor is
 built.

 And it only seems to affect auto IPv6 ORPorts.

 Does the issue still happen if the IPv6 address is much shorter than the
 maximum length?
 For example, does "ORPort [::1]:auto" give you a port of 1?
 You might need to set some custom directory authorities to be allowed to
 listen on an internal address.

--
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] #29801 [Core Tor/Tor]: Write a proposal for IPv6 "Happy Eyeballs" on Tor clients

[Tor Bug Tracker & Wiki]

#29801: Write a proposal for IPv6 "Happy Eyeballs" on Tor clients
-+-
 Reporter:  neel |  Owner:  neel
 Type:  enhancement  | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ipv6, prop299,   |  Actual Points:
  042-deferred-20190918  |
Parent ID:  #17835   | Points:
 Reviewer:  nickm, asn   |Sponsor:
-+-
Changes (by teor):

 * reviewer:  nickm => nickm, asn


Comment:

 I think these are the most recent reviews on tor-dev:
 https://lists.torproject.org/pipermail/tor-dev/2019-August/013959.html

--
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] #31039 [Core Tor/Tor]: Review proposal 306: IPv6 "Happy Eyeballs" for Tor clients

[Tor Bug Tracker & Wiki]

#31039: Review proposal 306: IPv6 "Happy Eyeballs" for Tor clients
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  task | Status:  closed
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  ipv6, prop299,   |  Actual Points:
  042-deferred-20190918  |
Parent ID:  #29801   | Points:
 Reviewer:  asn, nickm   |Sponsor:
-+-
Changes (by teor):

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


Comment:

 Let's just do this all in #29801.

--
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] #32588 [Core Tor/Tor]: Setting ORPort [ipv6]:auto mistakenly advertises port 94

[Tor Bug Tracker & Wiki]

#32588: Setting ORPort [ipv6]:auto mistakenly advertises port 94
---+---
 Reporter:  arma   |  Owner:  neel
 Type:  defect | Status:
   |  needs_information
 Priority:  Medium |  Milestone:  Tor:
   |  0.4.3.x-final
Component:  Core Tor/Tor   |Version:  Tor:
   |  0.4.1.6
 Severity:  Normal | Resolution:
 Keywords:  ipv6, memory-safety, security-low  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---
Changes (by teor):

 * keywords:  ipv6 => ipv6, memory-safety, security-low
 * status:  assigned => needs_information


Comment:

 The IPv6 descriptor code can never work for auto ports:
 https://github.com/torproject/tor/blob/master/src/feature/relay/router.c#L1991

 It should be like the IPv4 descriptor port code:
 https://github.com/torproject/tor/blob/master/src/feature/relay/router.c#L1978
 And call router_get_advertised_or_port_by_af() to get the IPv6 ORPort.

 Ideally, we should add a new router_get_advertised_ipv6_or_port()
 function, which searches for an address like this:
 https://github.com/torproject/tor/blob/master/src/feature/relay/router.c#L1991

 But searches for a port like this: (if the discovered port is 0)
 router_get_advertised_or_port_by_af(… , AF_INET6).

 I still can't work out how the port ends up being 94. Maybe we're
 overwriting some memory somewhere?
 I think we should try to find the memory issue, before we call this bug
 "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] #32672 [Core Tor/Tor]: Reject 0.2.9 and 0.4.0 in dirserv_rejects_tor_version()

[Tor Bug Tracker & Wiki]

#32672: Reject 0.2.9 and 0.4.0 in dirserv_rejects_tor_version()
-+-
 Reporter:  teor |  Owner:  neel
 Type:  task | Status:
 |  needs_information
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  043-should, 041-backport,|  Actual Points:
  042-backport, consider-backport-after- |
  authority-test, fast-fix, network-health   |
Parent ID:   | Points:  0.5
 Reviewer:  teor |Sponsor:
-+-

Comment (by dgoulet):

 > After 1 January 2020, we should reject all versions less than 0.3.5.

 Latest consensus:

 `<= 0.3.5 series: 781 [w: 6.53%]`

 Distribution:

 {{{
   16: 0.2.4 [0.02 %] (MAJOR)
   14: 0.2.5 [0.21 %] (MAJOR)
2: 0.2.6 [0.00 %] (MAJOR)
2: 0.2.7 [0.09 %] (MAJOR)
2: 0.2.8 [0.00 %] (MAJOR)
  640: 0.2.9 [5.48 %] (MAJOR)
   12: 0.3.0 [0.00 %] (MAJOR)
3: 0.3.1 [0.00 %] (MAJOR)
   23: 0.3.2 [0.15 %] (MAJOR)
8: 0.3.3 [0.05 %] (MAJOR)
   59: 0.3.4 [0.54 %] (MAJOR)
 }}}


 > find out how many relays are on unstable 0.4.0 versions

 `0.4.0 series: 520 [w: 11.23%]`

 Distribution:

 {{{
1: 0.4.0.0-alpha-dev [0.00 %]
2: 0.4.0.1-alpha [0.08 %]
1: 0.4.0.1-alpha-dev [0.00 %]
3: 0.4.0.2-alpha [0.19 %]
2: 0.4.0.3-alpha [0.01 %]
1: 0.4.0.4-rc[0.02 %]
  509: 0.4.0.5   [10.89 %]
1: 0.4.0.6   [0.04 %]
 }}}

--
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] #15302 [Applications/Tor Browser]: Tor browser doesn't recognize change of network interface which provides internet

[Tor Bug Tracker & Wiki]

#15302: Tor browser doesn't recognize change of network interface which provides
internet
--+--
 Reporter:  krichter  |  Owner:  tbb-team
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:  user disappeared
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by cypherpunks):

 If you have automated tests that don't show any problem with network
 interface change, than this ticket can be closed, yes.

--
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] #15302 [Applications/Tor Browser]: Tor browser doesn't recognize change of network interface which provides internet

[Tor Bug Tracker & Wiki]

#15302: Tor browser doesn't recognize change of network interface which provides
internet
--+--
 Reporter:  krichter  |  Owner:  tbb-team
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:  user disappeared
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by gk):

 Replying to [comment:6 cypherpunks]:
 > Shouldn't it be moved to `Core Tor`?

 Not sure. But at any rate that would not solve the problem that the user
 disappeared which makes it hard to decide where to move this ticket to.

--
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] #15302 [Applications/Tor Browser]: Tor browser doesn't recognize change of network interface which provides internet

[Tor Bug Tracker & Wiki]

#15302: Tor browser doesn't recognize change of network interface which provides
internet
--+--
 Reporter:  krichter  |  Owner:  tbb-team
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:  user disappeared
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by cypherpunks):

 Shouldn't it be moved to `Core Tor`?

--
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] #15302 [Applications/Tor Browser]: Tor browser doesn't recognize change of network interface which provides internet

[Tor Bug Tracker & Wiki]

#15302: Tor browser doesn't recognize change of network interface which provides
internet
--+--
 Reporter:  krichter  |  Owner:  tbb-team
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:  user disappeared
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by gk):

 * status:  needs_information => closed
 * resolution:   => user disappeared


--
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] #14795 [Applications/Tor Browser]: Windows Environmental Variables not usable in Profiles.ini when deploying tor browser across a domain

[Tor Bug Tracker & Wiki]

#14795: Windows Environmental Variables not usable in Profiles.ini when 
deploying
tor browser across a domain
-+-
 Reporter:  johnakabean  |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  windows, variables, windows  |  Actual Points:
  environment, windows environmental variables,  |
  windows variables  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by gk):

 * status:  needs_information => new


--
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] #14978 [Applications/Tor Browser]: Tor browser bundle random segfault

[Tor Bug Tracker & Wiki]

#14978: Tor browser bundle random segfault
--+--
 Reporter:  esmedoescode  |  Owner:  tbb-team
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:  user disappeared
 Keywords:  tbb-crash |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by gk):

 * status:  needs_information => closed
 * resolution:   => user disappeared


--
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] #14337 [Applications/Tor Browser]: Tabs Not All Shown in Normal View - no button to list rest

[Tor Bug Tracker & Wiki]

#14337: Tabs Not All Shown in Normal View - no button to list rest
--+
 Reporter:  plmlbn|  Owner:  tbb-team
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:  worksforme
 Keywords:  tbb-usability |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by gk):

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


Comment:

 Works for me.

--
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] #14279 [Applications/Tor Browser]: Tor Browser Bundle creates CGBitmapContextCreateImage in Mac OS X

[Tor Bug Tracker & Wiki]

#14279: Tor Browser Bundle creates CGBitmapContextCreateImage in Mac OS X
--+--
 Reporter:  qbi   |  Owner:  tbb-team
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:  user disappeared
 Keywords:  firefox, tor browser  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by gk):

 * status:  needs_information => closed
 * resolution:   => user disappeared


--
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] #13626 [Applications/Tor Browser]: Tor-browser-linux32-4.0.1 crash in Lubuntu

[Tor Bug Tracker & Wiki]

#13626: Tor-browser-linux32-4.0.1 crash in Lubuntu
--+--
 Reporter:  djjos |  Owner:  tbb-team
 Type:  defect| Status:  reopened
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by gk):

 * status:  closed => reopened
 * resolution:  user disappeared =>


--
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] #13626 [Applications/Tor Browser]: Tor-browser-linux32-4.0.1 crash in Lubuntu

[Tor Bug Tracker & Wiki]

#13626: Tor-browser-linux32-4.0.1 crash in Lubuntu
--+---
 Reporter:  djjos |  Owner:  tbb-team
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:  duplicate
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---
Changes (by gk):

 * status:  reopened => closed
 * resolution:   => duplicate


--
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] #13626 [Applications/Tor Browser]: Tor-browser-linux32-4.0.1 crash in Lubuntu

[Tor Bug Tracker & Wiki]

#13626: Tor-browser-linux32-4.0.1 crash in Lubuntu
--+--
 Reporter:  djjos |  Owner:  tbb-team
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:  user disappeared
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by gk):

 * status:  needs_information => closed
 * resolution:   => user disappeared


--
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] #13580 [Applications/Tor Browser]: Unable to run Tor browser

[Tor Bug Tracker & Wiki]

#13580: Unable to run Tor browser
--+--
 Reporter:  mrschwarz |  Owner:  tbb-team
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:  user disappeared
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by gk):

 * status:  needs_information => closed
 * resolution:   => user disappeared


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