Re: [tor-bugs] #30777 [Community/Outreach]: Run a "set up new bridges" campaign

[Tor Bug Tracker & Wiki]

#30777: Run a "set up new bridges" campaign
-+
 Reporter:  phw  |  Owner:  (none)
 Type:  project  | Status:  assigned
 Priority:  High |  Milestone:
Component:  Community/Outreach   |Version:
 Severity:  Normal   | Resolution:
 Keywords:  anti-censorship-roadmap  |  Actual Points:
Parent ID:   | Points:  3
 Reviewer:   |Sponsor:  Sponsor30-must
-+

Comment (by phw):

 Replying to [comment:9 phw]:
 > Replying to [comment:8 gaba]:
 > > Sounds good. Adding #30708 as a ticket then and we come back here once
 that is done.
 > [[br]]
 > We're done with the docker container and added instructions to our setup
 guide. We can now move forward with this ticket.
 [[br]]
 Actually, let's wait until #31153 is done as it will make bridge setup
 significantly easier. We hope to have the package in Debian stable by mid-
 September.

--
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] #31159 [Internal Services/Tor Sysadmin Team]: Monitor anti-censorship www services with prometheus

[Tor Bug Tracker & Wiki]

#31159: Monitor anti-censorship www services with prometheus
-+
 Reporter:  phw  |  Owner:  tpa
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:  #30152
   Points:  1|   Reviewer:
  Sponsor:   |
-+
 In the anti-censorship team we currently monitor
 
[https://trac.torproject.org/projects/tor/wiki/org/teams/AntiCensorshipTeam/InfrastructureMonitoring
 several services] with sysmon.  We recently discovered that sysmon doesn't
 seem to follow HTTP 301 redirects. This means that if a web service dies
 but the 301 redirect still works (e.g., BridgeDB is dead but its apache
 reverse proxy still works), sysmon won't notice.

 Now that prometheus is running, we should fill this monitoring gap by
 testing the following web sites:

 * https://bridges.torproject.org
 * https://snowflake.torproject.org
 * https://gettor.torproject.org

 Our test should ensure that these sites serve the content we expect, e.g.,
 make sure that bridges.tp.o contains the string "BridgeDB" in its HTML.
 Testing the HTTP status code does not suffice: if BridgeDB is down, the
 reverse proxy may still respond.

 I wonder if prometheus could also help us with #12802 by sending an email
 to bridges@tp.o and making sure that it responds with at least one bridge?

--
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] #31154 [Circumvention/Snowflake]: Ideas for hosting Tor Snowflake bridges with changing residential IP addresses?

[Tor Bug Tracker & Wiki]

#31154: Ideas for hosting Tor Snowflake bridges with changing residential IP
addresses?
-+
 Reporter:  subscriptionblocker  |  Owner:  (none)
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Circumvention/Snowflake  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+
Changes (by dcf):

 * cc: arlolra, cohosh, dcf, phw (added)


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

Re: [tor-bugs] #30126 [Applications/Tor Browser]: Make Tor Browser on macOS compatible with Apple's notarization

[Tor Bug Tracker & Wiki]

#30126: Make Tor Browser on macOS compatible with Apple's notarization
+--
 Reporter:  gk  |  Owner:  tbb-team
 Type:  task| Status:  new
 Priority:  Very High   |  Milestone:
Component:  Applications/Tor Browser|Version:
 Severity:  Normal  | Resolution:
 Keywords:  tbb-security, TorBrowserTeam201907  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--

Comment (by tom):

 If you have questions; :haik spent a considerable time investigating and
 deploying this for Mozilla.

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

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

[Tor Bug Tracker & Wiki]

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

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


Comment:

 > * Our broker currently has no IPv6 address.

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

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

Re: [tor-bugs] #31158 [- Select a component]: #31152 new defect Cannot make comments on Disqus

[Tor Bug Tracker & Wiki]

#31158: #31152 new defect Cannot make comments on Disqus
--+
 Reporter:  mwolfe|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by mwolfe):

 * Attachment "torversion8.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] #31158 [- Select a component]: #31152 new defect Cannot make comments on Disqus

[Tor Bug Tracker & Wiki]

#31158: #31152 new defect Cannot make comments on Disqus
--+
 Reporter:  mwolfe|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by mwolfe):

 * Attachment "disquserror.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] #31158 [- Select a component]: #31152 new defect Cannot make comments on Disqus

[Tor Bug Tracker & Wiki]

#31158: #31152 new defect Cannot make comments on Disqus
--+
 Reporter:  mwolfe|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by mwolfe):

 * Attachment "unsupported.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

[tor-bugs] #31158 [- Select a component]: #31152 new defect Cannot make comments on Disqus

[Tor Bug Tracker & Wiki]

#31158: #31152 new defect Cannot make comments on Disqus
+--
 Reporter:  mwolfe  |  Owner:  (none)
 Type:  defect  | Status:  new
 Priority:  Medium  |  Component:  - Select a component
  Version:  |   Severity:  Normal
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
 I was able to comment on Disqus using Tor until 2 days ago. My tor would
 not connect, so I upgraded to the alpha Tor, which connected, but could
 not comment. I tried going back, but my previous TorBrowser 8.5 could no
 longer comment. I was told to delete the TorBrower and download a new copy
 (which I did) but lots was left over. The last comment was if I could not
 delete the old version, start a new ticket.

 On the Macintosh, a lot is stored in the user's Library. Under Application
 Support is a TorBrowser file with lots in it. A new copy of Tor has all
 the old bookmarks and preferences. New copies could not comment on Disqus,
 because the login tab could not communicate with the comment tab, so one
 could log in once (takes a long time because of the Captcha that does not
 like Tor, but one can eventually get through), then the log in tab closes
 and you're back at the comment tab that thinks you are not logged in.
 Clicking login again causes the screen to flicker as it checks the login
 page and finds you're logged in, but you're back at the comment page
 unable to comment.

 I went back from TorBrowser 8.5 to 7.5, and I can comment. I then tried
 TorBrower 8.0 with all that was left in the Library, and could not
 comment, but I did get some interesting error messages (attached)

--
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] #27385 [Circumvention/Snowflake]: https://snowflake.torproject.org/embed is confusing

[Tor Bug Tracker & Wiki]

#27385: https://snowflake.torproject.org/embed is confusing
---+---
 Reporter:  cypherpunks3   |  Owner:  arlolra
 Type:  defect | Status:
   |  needs_review
 Priority:  High   |  Milestone:
Component:  Circumvention/Snowflake|Version:
 Severity:  Major  | Resolution:
 Keywords:  snowflake, ux-team, ex-sponsor-19  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
   |  Sponsor28-must
---+---
Changes (by arlolra):

 * status:  assigned => needs_review


Comment:

 Here's a patch that pretty much gets this done,
 
https://github.com/keroserene/snowflake/commit/12e7b92b4c59888cf43d2e1f0e5518df02b72bdc

 It's rather invasive and doesn't offer much in terms of explanation,
 sorry.

--
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] #30126 [Applications/Tor Browser]: Make Tor Browser on macOS compatible with Apple's notarization

[Tor Bug Tracker & Wiki]

#30126: Make Tor Browser on macOS compatible with Apple's notarization
+--
 Reporter:  gk  |  Owner:  tbb-team
 Type:  task| Status:  new
 Priority:  Very High   |  Milestone:
Component:  Applications/Tor Browser|Version:
 Severity:  Normal  | Resolution:
 Keywords:  tbb-security, TorBrowserTeam201907  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--

Comment (by mcs):

 Kathy and I need to do more research, but here are some things we learned
 so far.

 Additional resources:
 * https://stackoverflow.com/a/53121755/2517441 (assuming this answer is
 accurate, it provides detailed steps we will need to execute).
 * https://blog.zeplin.io/dev-journal-automate-notarizing-macos-apps-
 94b0b144ba9d (provides a good overview of a command line approach to
 notarization).
 *
 
https://developer.apple.com/documentation/security/notarizing_your_app_before_distribution/customizing_the_notarization_workflow

 Some of the requirements, as specified by Apple's documentation:
 * Link against the macOS 10.9 or later SDK (already done for Tor Browser).
 * Notarization requires Xcode 10 or later (maybe simply because we need an
 `xcrun` that supports the `altool`, and that first appeared in Xcode
 10.0).
 * Building a new app for notarization requires macOS 10.13.6 or later &
 Xcode 10 (macOS 10.13.6 is required for Xcode 10.0).
 * Stapling an app requires macOS 10.12 or later (but I guess we will have
 macOS 10.13.16 or newer anyway).
 * Enable code-signing for all of the executables you distribute (hopefully
 we already do this).
 * Use a Developer ID application, kernel extension, or installer
 certificate for your code-signing signature (a Mac Distribution or local
 development certificate will not work).
 * Include a secure timestamp with your code-signing signature (which means
 we need to include the `--timestamp` option when running the `codesign`
 tool).
 * Enable the Hardened Runtime capability for your app (how do we handle
 entitlements?)
 * Don't include the `com.apple.security.get-task-allow` entitlement with
 the value set to any variation of true (again, how do we add entitlements
 during our build process — if at all?)

 The following Firefox bug includes at least one patch related to
 entitlements, although the patches are for taskcluster and not core
 Firefox code: https://bugzilla.mozilla.org/show_bug.cgi?id=1471004

 It was suggested that we look at how Bitcoin Core is handling
 notarization, but all we found so far is this open issue:
 https://github.com/bitcoin/bitcoin/issues/15774

--
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] #14453 [Circumvention/BridgeDB]: Implement statistics gathering for number of Bridges-per-Transport in BridgeDB

[Tor Bug Tracker & Wiki]

#14453: Implement statistics gathering for number of Bridges-per-Transport in
BridgeDB
-+-
 Reporter:  isis |  Owner:  (none)
 Type:  task | Status:
 |  assigned
 Priority:  Medium   |  Milestone:
Component:  Circumvention/BridgeDB   |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-bridge, bridgedb, ex-sponsor-19  |  Actual Points:
Parent ID:   | Points:  5
 Reviewer:   |Sponsor:
 |  Sponsor30-must
-+-

Comment (by phw):

 Doesn't BridgeDB's assignments.log already contain exactly this
 information? Its format is:
 Fingerprint, distributor (e.g., HTTPS), IP version, flags, ring number,
 transports.

 For each bridge fingerprint, it tells us what transports the bridge is
 running. If assignments.log is indeed all we want, we may want to tackle
 this together with #29480.

--
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] #28015 [Applications/Tor Browser]: Brainstorm improved ux for orgs that want to give bridges to their people

[Tor Bug Tracker & Wiki]

#28015: Brainstorm improved ux for orgs that want to give bridges to their 
people
-+-
 Reporter:  arma |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ux-team, education, documentation,   |  Actual Points:
  ex-sponsor-19  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor30-must
-+-
Changes (by phw):

 * cc: phw (added)


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

[tor-bugs] #31157 [Circumvention/Snowflake]: Collect metrics about what type of proxies are running

[Tor Bug Tracker & Wiki]

#31157: Collect metrics about what type of proxies are running
-+
 Reporter:  cohosh   |  Owner:  (none)
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Circumvention/Snowflake  |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:
   Points:  3|   Reviewer:
  Sponsor:  Sponsor28|
-+
 Collect metrics about what type of proxies are running (e.g., are they the
 standalone proxy-go instances, webextensions, web badges, etc.) and add
 them to the current set of metrics that are displayed.

 This requires sending some additional information from the proxies to the
 broker in the initial poll step and will require whatever we decide to use
 for backwards compatable changes in the way different peices of snowflake
 interact with each other (#30704).

--
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] #29710 [Core Tor/sbws]: sbws reports fewer relays than torflow

[Tor Bug Tracker & Wiki]

#29710: sbws reports fewer relays than torflow
---+---
 Reporter:  starlight  |  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:  sbws: unspecified
Component:  Core Tor/sbws  |Version:  sbws: unspecified
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---
Changes (by pastly):

 * cc: pastly (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] #31154 [Circumvention/Snowflake]: Ideas for hosting Tor Snowflake bridges with changing residential IP addresses?

[Tor Bug Tracker & Wiki]

#31154: Ideas for hosting Tor Snowflake bridges with changing residential IP
addresses?
-+
 Reporter:  subscriptionblocker  |  Owner:  (none)
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Circumvention/Snowflake  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+
Changes (by nickm):

 * component:  Core Tor => Circumvention/Snowflake


--
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] #31156 [Core Tor/Tor]: Add support of TBytes keyword to torrc for AccountingMax setting (and maybe others)

[Tor Bug Tracker & Wiki]

#31156: Add support of TBytes keyword to torrc for AccountingMax setting (and 
maybe
others)
--+
 Reporter:  tla   |  Owner:  (none)
 Type:  enhancement   | Status:  new
 Priority:  Low   |  Milestone:  Tor: 0.4.2.x-final
Component:  Core Tor/Tor  |Version:  Tor: 0.2.9.17
 Severity:  Minor | Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by nickm):

 * milestone:   => Tor: 0.4.2.x-final


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

Re: [tor-bugs] #31149 [Core Tor/Tor]: Tor is stuck at "Loading Network Status"

[Tor Bug Tracker & Wiki]

#31149: Tor is stuck at "Loading Network Status"
--+
 Reporter:  bornadx   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  High  |  Milestone:  Tor: 0.4.2.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by nickm):

 * milestone:   => Tor: 0.4.2.x-final


Comment:

 {{{
 7/12/19, 17:45:37.240 [NOTICE] DisableNetwork is set. Tor will not make or
 accept non-control network connections. Shutting down all existing
 connections.
 7/12/19, 17:45:37.240 [NOTICE] Opening Socks listener on 127.0.0.1:9150
 7/12/19, 17:45:37.240 [NOTICE] Opened Socks listener on 127.0.0.1:9150
 7/12/19, 17:45:37.853 [WARN] Managed proxy at
 'TorBrowser\Tor\PluggableTransports\terminateprocess-buffer.exe' reported:
 2019/07/12 17:45:37 running firefox command
 ["C:\\Users\\Administrator\\Desktop\\Tor Browser\\Browser\\firefox.exe" "
 --invisible" "-no-remote" "-profile"
 "C:\\Users\\Administrator\\Desktop\\Tor
 Browser\\Browser\\TorBrowser\\Data\\Browser\\profile.meek-http-helper"]
 7/12/19, 17:45:37.853 [WARN] Managed proxy at
 'TorBrowser\Tor\PluggableTransports\terminateprocess-buffer.exe' reported:
 2019/07/12 17:45:37 firefox started with pid 2156
 7/12/19, 17:45:38.867 [WARN] Managed proxy at
 'TorBrowser\Tor\PluggableTransports\terminateprocess-buffer.exe' reported:
 2019/07/12 17:45:38 running meek-client command
 ["TorBrowser\\Tor\\PluggableTransports\\meek-client.exe" "--helper"
 "127.0.0.1:64639"]
 7/12/19, 17:45:38.867 [WARN] Managed proxy at
 'TorBrowser\Tor\PluggableTransports\terminateprocess-buffer.exe' reported:
 2019/07/12 17:45:38 meek-client started with pid 2600
 7/12/19, 17:45:38.868 [WARN] Managed proxy at
 'TorBrowser\Tor\PluggableTransports\terminateprocess-buffer.exe' reported:
 2019/07/12 17:45:38 using helper on 127.0.0.1:64639
 7/12/19, 17:45:38.868 [WARN] Managed proxy at
 'TorBrowser\Tor\PluggableTransports\terminateprocess-buffer.exe' reported:
 2019/07/12 17:45:38 listening on 127.0.0.1:64640
 7/12/19, 17:45:38.869 [NOTICE] Bootstrapped 1% (conn_pt): Connecting to
 pluggable transport
 7/12/19, 17:45:38.888 [NOTICE] Bootstrapped 2% (conn_done_pt): Connected
 to pluggable transport
 7/12/19, 17:45:38.890 [NOTICE] Bootstrapped 10% (conn_done): Connected to
 a relay
 7/12/19, 17:45:45.944 [NOTICE] Bootstrapped 14% (handshake): Handshaking
 with a relay
 7/12/19, 17:45:50.732 [NOTICE] Bootstrapped 15% (handshake_done):
 Handshake with a relay done
 7/12/19, 17:45:50.733 [NOTICE] Bootstrapped 20% (onehop_create):
 Establishing an encrypted directory connection
 7/12/19, 17:45:53.950 [NOTICE] Bootstrapped 25% (requesting_status):
 Asking for networkstatus consensus
 7/12/19, 17:45:54.174 [NOTICE] Delaying directory fetches: No running
 bridges
 7/12/19, 17:46:03.240 [NOTICE] Bootstrapped 30% (loading_status): Loading
 networkstatus consensus
 7/12/19, 17:46:03.360 [NOTICE] new bridge descriptor 'cymrubridge02'
 (fresh): $97700DFE9F483596DDA6264C4D7DF7641E1E39CE~cymrubridge02 at
 0.0.2.0
 7/12/19, 17:46:26.360 [WARN] Refusing to apply consensus diff because the
 base consensus doesn't match the digest as found in the consensus diff
 header.
 7/12/19, 17:46:26.360 [WARN] Expected:
 31A519B72EC64D5CFC5340E47D34F15B815674E6833F447C344C0F34F66D1B69; found:
 A7967A9A0A73D3197EA6A9DADAC9667918E4BE4A49AF56E19317FB1AD0255648
 7/12/19, 17:46:26.361 [WARN] Could not apply consensus diff received from
 server '0.0.2.0:2'
 7/12/19, 17:47:25.190 [WARN] Refusing to apply consensus diff because the
 base consensus doesn't match the digest as found in the consensus diff
 header.
 7/12/19, 17:47:25.190 [WARN] Expected:
 31A519B72EC64D5CFC5340E47D34F15B815674E6833F447C344C0F34F66D1B69; found:
 A7967A9A0A73D3197EA6A9DADAC9667918E4BE4A49AF56E19317FB1AD0255648
 7/12/19, 17:47:25.191 [WARN] Could not apply consensus diff received from
 server '0.0.2.0:2'
 7/12/19, 17:47:25.191 [WARN] Refusing to apply consensus diff because the
 base consensus doesn't match the digest as found in the consensus diff
 header.
 7/12/19, 17:47:25.191 [WARN] Expected:
 31A519B72EC64D5CFC5340E47D34F15B815674E6833F447C344C0F34F66D1B69; found:
 A7967A9A0A73D3197EA6A9DADAC9667918E4BE4A49AF56E19317FB1AD0255648
 7/12/19, 17:47:25.191 [WARN] Could not apply consensus diff received from
 server '0.0.2.0: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] #31148 [- Select a component]: Tor is stuck at "Loading Network Status"

[Tor Bug Tracker & Wiki]

#31148: Tor is stuck at "Loading Network Status"
--+---
 Reporter:  bornadx   |  Owner:  (none)
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal| Resolution:  duplicate
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---
Changes (by nickm):

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


Comment:

 Instead see #31149

--
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] #31089 [Core Tor/Tor]: Consider using data-URI to embed how_tor_works_thumb.png image into tor-exit-notice.html

[Tor Bug Tracker & Wiki]

#31089: Consider using data-URI to embed how_tor_works_thumb.png image into tor-
exit-notice.html
--+
 Reporter:  rl1987|  Owner:  (none)
 Type:  enhancement   | Status:  needs_review
 Priority:  Low   |  Milestone:  Tor: 0.4.2.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Trivial   | Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by nickm):

 * milestone:  Tor: unspecified => Tor: 0.4.2.x-final


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

Re: [tor-bugs] #23818 [Core Tor/Tor]: Make v3 single onion services retry failed connections with a 3-hop path

[Tor Bug Tracker & Wiki]

#23818: Make v3 single onion services retry failed connections with a 3-hop path
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.2.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  v3-onion-service-feature-parity, |  Actual Points:
  prop224, tor-hs, single-onion, ipv6,   |
  034-triage-20180328, 034-removed-20180328  |
Parent ID:  #23493   | Points:  1
 Reviewer:   |Sponsor:
 |  Sponsor27-must
-+-
Changes (by nickm):

 * milestone:  Tor: unspecified => Tor: 0.4.2.x-final


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

Re: [tor-bugs] #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.2.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  ipv6, prop299  |  Actual Points:
Parent ID:  #17835 | Points:
 Reviewer:  nickm  |Sponsor:
---+
Changes (by nickm):

 * milestone:  Tor: unspecified => Tor: 0.4.2.x-final


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

Re: [tor-bugs] #31152 [Applications/Tor Browser]: Disqus broken again

[Tor Bug Tracker & Wiki]

#31152: Disqus broken again
--+--
 Reporter:  mwolfe|  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by mwolfe):

 Replying to [comment:1 cypherpunks]:
 > How to test properly:
 > 1. Delete everything.
 > 2. Make a new installation of Tor Browser Alpha.
 > 3. Test.
 > If it doesn't work, enable 3rd-party cookies, restart, test.
 > If it doesn't work, disable NoScript, restart, test.
 > If it doesn't work, remove NoScript, restart, test.
 > If it doesn't work, report here.

 TorBrowser-9.0a works fine on Windows, but on OSX 10.11.6, with
 TorBrowser-8.5.4-osx64 I have deleted everything, removed NoScript, set
 enable all cookies, turned Private Mode off, and when I click Login
 Disqus, after many, many Captchas I get logged in on the login tab and
 returned to the comment tab, where I am not logged in. If I click Login
 Disqus again, I do not see the login tab, it goes there, sees I'm logged
 in on the login tab, and returns me to the comment tab (none of which
 shows on the screen, I just see the comment tab) where I am not logged in.

 I still have a copy of TorBrowser 7.5.6, where I can comment on Disqus. I
 think I could comment on TorBrowser 8.4 (but TorBrowser 8.4 knows not to
 let me install it, since a newer version is available). But on TorBrowser
 8.5.4, no matter what I do, the Disqus login tab cannot communicate with
 the Disqus comment tab, and likewise TorBrowser-9.0a on OSX 10.11.6

--
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] #31136 [Core Tor/Tor]: tor_bug_occurred_() channel_tls_handle_cell: This line should not have been reached.

[Tor Bug Tracker & Wiki]

#31136: tor_bug_occurred_() channel_tls_handle_cell: This line should not have 
been
reached.
-+-
 Reporter:  fingau   |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.2.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.5.8
 Severity:  Normal   | Resolution:
 Keywords:  tor-relay, tor-channel,  |  Actual Points:
  041-backport 040-backport 035-backport |
Parent ID:  #31107   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * keywords:  tor-relay, tor-channel => tor-relay, tor-channel, 041-backport
 040-backport 035-backport
 * milestone:   => Tor: 0.4.2.x-final


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

Re: [tor-bugs] #31152 [Applications/Tor Browser]: Disqus broken again

[Tor Bug Tracker & Wiki]

#31152: Disqus broken again
--+--
 Reporter:  mwolfe|  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by nickm):

 * owner:  (none) => tbb-team
 * component:  - Select a component => Applications/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] #31155 [Applications/Tor Browser]: Privacy with TOR

[Tor Bug Tracker & Wiki]

#31155: Privacy with TOR
--+--
 Reporter:  Webster   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by nickm):

 * owner:  (none) => tbb-team
 * component:  - Select a component => Applications/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

[tor-bugs] #31156 [Core Tor/Tor]: Add support of TBytes keyword to torrc for AccountingMax setting (and maybe others)

[Tor Bug Tracker & Wiki]

#31156: Add support of TBytes keyword to torrc for AccountingMax setting (and 
maybe
others)
---+--
 Reporter:  tla|  Owner:  (none)
 Type:  enhancement| Status:  new
 Priority:  Low|  Component:  Core Tor/Tor
  Version:  Tor: 0.2.9.17  |   Severity:  Minor
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--
 Happening on Debian 9 with Tor 0.2.9.16 from the standard apt repo.
 (Sorry, if this is already resolved in newer versions. In that case just
 close and ignore.)

 Syslog output:


 {{{
 Jul 14 10:50:38 systemd[1]: Starting Anonymizing overlay network for
 TCP...
 Jul 14 10:50:39 tor[530]: Jul 14 10:50:39.082 [notice] Tor 0.2.9.16 (git-
 9ef571339967c1e5) running on Linux with Libevent 2.0.21-stable, OpenSSL
 1.1.0k and Zlib 1.2.8.
 Jul 14 10:50:39 tor[530]: Jul 14 10:50:39.082 [notice] Tor can't help you
 if you use it wrong! Learn how to be safe at
 https://www.torproject.org/download/download#warning
 Jul 14 10:50:39 tor[530]: Jul 14 10:50:39.082 [notice] Read configuration
 file "/usr/share/tor/tor-service-defaults-torrc".
 Jul 14 10:50:39 tor[530]: Jul 14 10:50:39.082 [notice] Read configuration
 file "/etc/tor/torrc".
 Jul 14 10:50:39 tor[530]: Jul 14 10:50:39.085 [warn] Unknown unit
 'TBytes'.
 Jul 14 10:50:39 tor[530]: Jul 14 10:50:39.085 [warn] Failed to
 parse/validate config: Value 'AccountingMax 5 TBytes' is malformed or out
 of bounds.
 Jul 14 10:50:39 tor[530]: Jul 14 10:50:39.085 [err] Reading config failed
 --see warnings above.
 Jul 14 10:50:39 systemd[1]: tor@default.service: Control process exited,
 code=exited status=1
 Jul 14 10:50:39 systemd[1]: Failed to start Anonymizing overlay network
 for TCP.

 }}}

 Additionally, please note that /var/tor/log didn't give any hint of this,
 instead it went to syslog. Suboptimal.

--
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] #28582 [Core Tor/Tor]: Document the load-balancing goal for sbws

[Tor Bug Tracker & Wiki]

#28582: Document the load-balancing goal for sbws
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  task | Status:
 |  needs_information
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  teor-backlog, tor-spec, sbws-1.0 |  Actual Points:  0.2
  -nice-moved-20181128, teor-|
  unreached-2019-03-08, no-changes-version,  |
  docs, sbws-11x-final-removed-20190312, doc,|
  041-deferred-20190530  |
Parent ID:   | Points:  0.2
 Reviewer:   |Sponsor:
-+-

Comment (by juga):

 Replying to [comment:19 teor]:
 > Hi Mike, Juga,
 >
 > I'm not sure what you are asking me to do to resolve this ticket:

 My intention asking Mike to add this link was to just keep track on
 documentation that could be useful for this ticket and i don't want to
 forget about but to think about.
 My intention was not to make you do anything nor to resolve this ticket.

 >
 > Replying to [comment:18 mikeperry]:
 > > Juga asked that I add the metrics link for load balancing evaluation
 to this ticket:
 
https://trac.torproject.org/projects/tor/wiki/org/roadmaps/CoreTor/PerformanceMetrics#BalancingMetrics
 >
 > Do either of you want to write the sbws load balancing goals and submit
 a pull request for the spec?
 >
 > Do you want me to wait to write the sbws load balancing goals until
 after the load balancing evaluation?
 >
 > Do you want me to change the draft load balancing goals in the ticket
 description, based on Mike's "healthy network" descriptions in the load
 balancing evaluation?
 >
 > Or something else?
 >
 > I'm happy to do whatever you think is best.

 As i say, my intention is not to make you do anything. Sorry for the
 missunderstanding.

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