[tor-bugs] #25317 [Metrics/CollecTor]: Enable webstats to process large (> 2G) logfiles

[Tor Bug Tracker & Wiki]

#25317: Enable webstats to process large (> 2G) logfiles
---+--
 Reporter:  iwakeh |  Owner:  iwakeh
 Type:  defect | Status:  assigned
 Priority:  High   |  Milestone:
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal |   Keywords:
Actual Points: |  Parent ID:
   Points: |   Reviewer:
  Sponsor: |
---+--
 Quote from #25161, comment 12:
Looking at the stack trace and the input log files, I noticed that two
 log files are larger than 2G when decompressed:

 {{{
 3.2G in/webstats/archeotrichon.torproject.org/dist.torproject.org-
 access.log-20160531
 584K in/webstats/archeotrichon.torproject.org/dist.torproject.org-
 access.log-20160531.xz
 2.1G in/webstats/archeotrichon.torproject.org/dist.torproject.org-
 access.log-20160601
 404K in/webstats/archeotrichon.torproject.org/dist.torproject.org-
 access.log-20160601.xz
 }}}

   I just ran another bulk import with just those two files as import and
 ran into the same exception.

   It seems like we shouldn't attempt to decompress these files into a
 `byte[]` in `FileType.decompress`, because Java can only handle arrays
 with up to 2 billion elements:
 https://en.wikipedia.org/wiki/Criticism_of_Java#Large_arrays . Maybe we
 should work with streams there, not `byte[]`.

--
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] #24879 [Applications/Tor Browser]: Set 'fetch: 1' by default for nightly builds

[Tor Bug Tracker & Wiki]

#24879: Set 'fetch: 1' by default for nightly builds
+--
 Reporter:  boklm   |  Owner:  tbb-team
 Type:  task| Status:  needs_review
 Priority:  Medium  |  Milestone:
Component:  Applications/Tor Browser|Version:
 Severity:  Normal  | Resolution:
 Keywords:  tbb-rbm, TorBrowserTeam201802R  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by boklm):

 * status:  needs_revision => needs_review
 * keywords:  tbb-rbm, TorBrowserTeam201802 => tbb-rbm,
   TorBrowserTeam201802R


Comment:

 Replying to [comment:6 gk]:
 > Thanks. It seems we want to have "if the selected commit" instead of "if
 the select commit"?

 I updated this in branch `bug_24879_v5`:
 https://gitweb.torproject.org/user/boklm/tor-browser-
 build.git/commit/?h=bug_24879_v5=95b5c738d8e1a11596e652363e801e500c5733de

--
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] #25161 [Metrics/CollecTor]: Fix another memory problem with the webstats bulk import

[Tor Bug Tracker & Wiki]

#25161: Fix another memory problem with the webstats bulk import
---+---
 Reporter:  karsten|  Owner:  iwakeh
 Type:  defect | Status:  needs_information
 Priority:  Medium |  Milestone:
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---
Changes (by iwakeh):

 * status:  assigned => needs_information


Comment:

 Thanks, for identifying the new issue!

 I just created a new ticket for this large log issue, #25317.

 This ticket here should rather handle the import of a number of lesser
 sized logs.

 In order to see what other work is necessary regarding the import:
 Could you run the import again without the problematic files and report
 the memory use throughout the import?
 (That can be achieved by using jconsole and saving the values 'behind' the
 memory graph.)

--
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] #25161 [Metrics/CollecTor]: Fix any memory problem caused by number of log files to be imported by the webstats module

[Tor Bug Tracker & Wiki]

#25161: Fix any memory problem caused by number of log files to be imported by 
the
webstats module
---+---
 Reporter:  karsten|  Owner:  iwakeh
 Type:  defect | Status:  needs_information
 Priority:  Medium |  Milestone:
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---

Comment (by karsten):

 Replying to [comment:13 iwakeh]:
 > Thanks, for identifying the new issue!
 >
 > I just created a new ticket for this large log issue, #25317.
 >
 > This ticket here should rather handle the import of a number of lesser
 sized logs.

 Okay.

 > In order to see what other work is necessary regarding the import:
 > Could you run the import again without the problematic files and report
 the memory use throughout the import?
 > (That can be achieved by using jconsole and saving the values 'behind'
 the memory graph.)

 Yes, I'll re-run the import without those two files. If you have a
 specific command you want me to run for memory usage monitoring, let me
 know here in the next 15 minutes. Otherwise I'll do my best. :)

--
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] #22612 [Applications/Tor Browser]: Provide a list sha256's for verified binary downloads from mirrors

[Tor Bug Tracker & Wiki]

#22612: Provide a list sha256's for verified binary downloads from mirrors
+--
 Reporter:  BenjaminCarr|  Owner:  tbb-team
 Type:  enhancement | Status:  needs_review
 Priority:  Medium  |  Milestone:
Component:  Applications/Tor Browser|Version:
 Severity:  Normal  | Resolution:
 Keywords:  tbb-rbm, TorBrowserTeam201802R  |  Actual Points:
Parent ID:  #20892  | Points:
 Reviewer:  |Sponsor:
+--

Comment (by boklm):

 Maybe we can add an `export LC_ALL=C` in the script so that the `sort`
 does not depend on the locale?

 Otherwise the patch looks good.

--
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] #25161 [Metrics/CollecTor]: Fix any memory problem caused by number of log files to be imported by the webstats module

[Tor Bug Tracker & Wiki]

#25161: Fix any memory problem caused by number of log files to be imported by 
the
webstats module
---+---
 Reporter:  karsten|  Owner:  iwakeh
 Type:  defect | Status:  needs_information
 Priority:  Medium |  Milestone:
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---

Comment (by iwakeh):

 Replying to [comment:15 karsten]:
 >...
 > > In order to see what other work is necessary regarding the import:
 > > Could you run the import again without the problematic files and
 report the memory use throughout the import?
 > > (That can be achieved by using jconsole and saving the values 'behind'
 the memory graph.)
 >
 > Yes, I'll re-run the import without those two files. If you have a
 specific command you want me to run for memory usage monitoring, let me
 know here in the next 15 minutes. Otherwise I'll do my best. :)

 No particular command: I would trust you to monitor 'top' and report on
 that ;-)
 I like to use jconsole for memory monitoring and the graphs can be
 exported easily.

--
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] #25275 [Internal Services/Service - git]: Please delete tag collector-1.5.0 in collector.git

[Tor Bug Tracker & Wiki]

#25275: Please delete tag collector-1.5.0 in collector.git
-+
 Reporter:  karsten  |  Owner:  tor-gitadm
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service - git  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+

Comment (by karsten):

 Pretty please. :)

--
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] #25161 [Metrics/CollecTor]: Fix any memory problem caused by number of log files to be imported by the webstats module (was: Fix another memory problem with the webstats bulk import)

[Tor Bug Tracker & Wiki]

#25161: Fix any memory problem caused by number of log files to be imported by 
the
webstats module
---+---
 Reporter:  karsten|  Owner:  iwakeh
 Type:  defect | Status:  needs_information
 Priority:  Medium |  Milestone:
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---

Old description:

> I'm running a modified CollecTor that sanitizes webstats with some tweaks
> towards bulk importing existing webstats. In particular, it reads files
> in slices of 10 MiB plus another 2 MiB that overlap with the next slice.
> I just pushed the changes [https://gitweb.torproject.org/karsten/metrics-
> db.git/commit/?h=webstats-
> slices=6c1a266d726ceedf4518e7521a6ed58a6764aca4 here].
>
> First of all, the runtime is okay. Not great, but okay. It takes 36
> minutes to sanitize 10 MiB. We have 927 MiB of files, so 93 slices, which
> is going to take ~2.5 days.
>
> However, I ran into an out-of-memory problem at the 6th slice:
>
> {{{
> 2018-02-06 13:30:36,499 INFO o.t.c.w.SanitizeWeblogs:116 Processing 20
> logs for dist.torproject.org on archeotrichon.torproject.org.
> 2018-02-06 13:40:28,968 ERROR o.t.c.c.CollecTorMain:71 The webstats
> module failed: null
> java.lang.OutOfMemoryError: null
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at
> java.util.concurrent.ForkJoinTask.getThrowableException(ForkJoinTask.java:598)
> at
> java.util.concurrent.ForkJoinTask.reportException(ForkJoinTask.java:677)
> at
> java.util.concurrent.ForkJoinTask.invoke(ForkJoinTask.java:735)
> at
> java.util.stream.ForEachOps$ForEachOp.evaluateParallel(ForEachOps.java:160)
> at
> java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateParallel(ForEachOps.java:174)
> at
> java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:233)
> at
> java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418)
> at
> org.torproject.collector.webstats.SanitizeWeblogs.findCleanWrite(SanitizeWeblogs.java:127)
> at
> org.torproject.collector.webstats.SanitizeWeblogs.startProcessing(SanitizeWeblogs.java:91)
> at
> org.torproject.collector.cron.CollecTorMain.run(CollecTorMain.java:67)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.OutOfMemoryError: Requested array size exceeds VM
> limit
> at
> java.lang.StringCoding$StringEncoder.encode(StringCoding.java:300)
> at java.lang.StringCoding.encode(StringCoding.java:344)
> at java.lang.StringCoding.encode(StringCoding.java:387)
> at java.lang.String.getBytes(String.java:958)
> at
> org.torproject.descriptor.log.LogDescriptorImpl.collectionToBytes(LogDescriptorImpl.java:119)
> at
> org.torproject.descriptor.log.WebServerAccessLogImpl.(WebServerAccessLogImpl.java:72)
> at
> org.torproject.collector.webstats.SanitizeWeblogs.storeSanitized(SanitizeWeblogs.java:147)
> at
> org.torproject.collector.webstats.SanitizeWeblogs.lambda$findCleanWrite$3(SanitizeWeblogs.java:127)
> at
> org.torproject.collector.webstats.SanitizeWeblogs$$Lambda$38/1233367077.accept(Unknown
> Source)
> at
> java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:184)
> at
> java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175)
> at
> java.util.concurrent.ConcurrentHashMap$EntrySpliterator.forEachRemaining(ConcurrentHashMap.java:3606)
> at
> java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
> at
> 

Re: [tor-bugs] #25316 [Core Tor/Tor]: Assertion failure in scale_active_circuits

[Tor Bug Tracker & Wiki]

#25316: Assertion failure in scale_active_circuits
-+
 Reporter:  Logforme |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  High |  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor |Version:  Tor: 0.3.2.9
 Severity:  Major| Resolution:
 Keywords:  crash, must-033  |  Actual Points:
Parent ID:   | Points:  0.5
 Reviewer:   |Sponsor:
-+
Changes (by teor):

 * severity:  Normal => Major
 * priority:  Medium => High
 * points:   => 0.5
 * version:   => Tor: 0.3.2.9
 * milestone:   => Tor: 0.3.3.x-final
 * keywords:   => crash, must-033


--
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] #25318 [Applications/Quality Assurance and Testing]: Add Tor Browser nightly builds email notification

[Tor Bug Tracker & Wiki]

#25318: Add Tor Browser nightly builds email notification
-+-
 Reporter:  boklm|  Owner:  boklm
 Type:  task | Status:  assigned
 Priority:  Medium   |  Milestone:
Component:   |Version:
  Applications/Quality Assurance |
  and Testing|   Keywords:  TorBrowserTeam201802,
 Severity:  Normal   |  boklm201802
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 When the nightly builds finish, an email should be sent with the status of
 the build.

--
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] #24879 [Applications/Tor Browser]: Set 'fetch: 1' by default for nightly builds

[Tor Bug Tracker & Wiki]

#24879: Set 'fetch: 1' by default for nightly builds
+--
 Reporter:  boklm   |  Owner:  tbb-team
 Type:  task| Status:  closed
 Priority:  Medium  |  Milestone:
Component:  Applications/Tor Browser|Version:
 Severity:  Normal  | Resolution:  fixed
 Keywords:  tbb-rbm, TorBrowserTeam201802R  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by gk):

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


Comment:

 Looks good. Merged to `master` (commit
 95b5c738d8e1a11596e652363e801e500c5733de).

--
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] #15599 [Applications/Tor Browser]: Range requests used by pdfjs are not isolated to URL bar domain

[Tor Bug Tracker & Wiki]

#15599: Range requests used by pdfjs are not isolated to URL bar domain
-+-
 Reporter:  gk   |  Owner:
 |  pospeselr
 Type:  defect   | Status:  closed
 Priority:  High |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  tbb-linkability, |  Actual Points:
  TorBrowserTeam201802R  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by gk):

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


Comment:

 Let's test the patch as-is in the alpha. I am skeptical that the benefit
 is worth the usability penalty. If we think it is okay then I think the
 patch idea brought up by mcs is the better one.

 Applied to `tor-browser-build`'s `master` as commit
 7db15759a31a7381d0a43b1a40373cd9f970210a.

--
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] #25321 [Applications/Tor Browser]: Unable to comment on independent.co.uk

[Tor Bug Tracker & Wiki]

#25321: Unable to comment on independent.co.uk
--+--
 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 cypherpunks):

 * 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] #25319 [Core Tor/Tor]: commit 4438ef32 breaks tor macOS cross builds

[Tor Bug Tracker & Wiki]

#25319: commit 4438ef32 breaks tor macOS cross builds
--+
 Reporter:  gk|  Owner:  nickm
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:  Tor: 0.3.4.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:  macos |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by nickm):

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


Comment:

 Fixed by reverting the test_address.c change in
 fc22bcadb51bcabb9b9c16a9768adbe86788b7f1.  I've tested it on my osx
 laptop, and it works for me. Then again, the old version also worked for
 me: apparently this behavior is not present in all versions of the mac
 headers.

--
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] #25055 [Core Tor/Tor]: string_is_valid_hostname() returns true for IPv4 addresses

[Tor Bug Tracker & Wiki]

#25055: string_is_valid_hostname() returns true for IPv4 addresses
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.2.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  IPv6 IPv4 tor-dns 032-backport   |  Actual Points:
  must-033   |
Parent ID:  #25036   | Points:  1
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * status:  merge_ready => needs_revision


Comment:

 The `tor_assert(len > 0)` check in `string_is_valid_dest()` makes me quite
 nervous.  There's nothing in the documentation for that function that says
 you can't call it with "" as an argument.  It would make much more sense
 to me if the function just returns 0 when `len == 0`.

 I don't understand why you changed the check `do {} while` loop from
 `result` to `result > 0`.

--
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] #23136 [Applications/Tor Launcher]: moat integration (fetch bridges for the user)

[Tor Bug Tracker & Wiki]

#23136: moat integration (fetch bridges for the user)
---+--
 Reporter:  mcs|  Owner:  brade
 Type:  defect | Status:  needs_review
 Priority:  Very High  |  Milestone:
Component:  Applications/Tor Launcher  |Version:
 Severity:  Normal | Resolution:
 Keywords:  TorBrowserTeam201802R  |  Actual Points:
Parent ID:  #24689 | Points:
 Reviewer: |Sponsor:  Sponsor4
---+--

Comment (by mcs):

 Replying to [comment:40 gk]:
 > I think we should try to handle this case more gracefully. Ideally, I
 think meek would be shut down again if I clicked the `Cancel` button
 (assuming that's not happening at the moment and the underlying issue).

 Agreed, and the potential for this kind of problem is what led us to use
 the TOR_PT_EXIT_ON_STDIN_CLOSE mechanism. In fact, Kathy and I thought
 this was working 100% of the time... but I was able to reproduce the
 problem you describe on Linux just now. As you suspected, the problem is
 that the meek processes are not shutting down. We are investigating.

--
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] #16849 [Core Tor/Tor]: clear_status_flags_on_sybil might want to clear more flags

[Tor Bug Tracker & Wiki]

#16849: clear_status_flags_on_sybil might want to clear more flags
-+-
 Reporter:  teor |  Owner:
 |  ffmancera
 Type:  defect   | Status:
 |  needs_revision
 Priority:  High |  Milestone:  Tor:
 |  0.3.4.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  easy, SponsorS-deferred, technical-  |  Actual Points:
  debt, tor-dirauth, pending-disaster, review-   |
  group-32   |
Parent ID:   | Points:  small
 Reviewer:  teor, nickm  |Sponsor:
-+-

Comment (by ffmancera):

 As teor and I discussed at #tor-dev, doing the zero-and-copy approach will
 avoid new similar issues in the future with new flags, but we need to find
 out a way to check out in a unit test that we are not clearing other
 important struct fields.

 Also, there is no new flags added to the routerstatus_t struct.

--
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] #25312 [Core Tor/Tor]: circ: We can pick an active circuit that is marked for close

[Tor Bug Tracker & Wiki]

#25312: circ: We can pick an active circuit that is marked for close
---+
 Reporter:  dgoulet|  Owner:  dgoulet
 Type:  defect | Status:  assigned
 Priority:  Medium |  Milestone:  Tor: 0.3.4.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  tor-cmux, tor-circuit  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+

Comment (by dgoulet):

 Datapoint: after one night of running this, I see more type of cells now,
 DATA, EXTENDED and BEGIN. Thus, this clearly affects any type of circuits.

--
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] #22612 [Applications/Tor Browser]: Provide a list sha256's for verified binary downloads from mirrors

[Tor Bug Tracker & Wiki]

#22612: Provide a list sha256's for verified binary downloads from mirrors
+--
 Reporter:  BenjaminCarr|  Owner:  tbb-team
 Type:  enhancement | Status:  closed
 Priority:  Medium  |  Milestone:
Component:  Applications/Tor Browser|Version:
 Severity:  Normal  | Resolution:  fixed
 Keywords:  tbb-rbm, TorBrowserTeam201802R  |  Actual Points:
Parent ID:  #20892  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by gk):

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


Comment:

 Replying to [comment:15 boklm]:
 > Maybe we can add an `export LC_ALL=C` in the script so that the `sort`
 does not depend on the locale?
 >
 > Otherwise the patch looks good.

 Thanks. I've fixed that and pushed the result (commit
 011e0d3d3da5263efa29b9a5963caa083f4c3ff5) to `master`.

--
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] #22346 [Metrics/Statistics]: Investigate drop in Tor Browser update pings in early 2017 and 2018

[Tor Bug Tracker & Wiki]

#22346: Investigate drop in Tor Browser update pings in early 2017 and 2018
+--
 Reporter:  cypherpunks |  Owner:  metrics-team
 Type:  defect  | Status:  new
 Priority:  Medium  |  Milestone:
Component:  Metrics/Statistics  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--

Comment (by boklm):

 The drop from 2018-01-24 seems to be related to the release of Tor Browser
 7.5. However I can't find any change between 7.0.11 and 7.5 that could
 explain that. The `app.update.*` prefs seems to be the same in both
 versions.

--
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] #25321 [Applications/Tor Browser]: Unable to comment on independent.co.uk

[Tor Bug Tracker & Wiki]

#25321: Unable to comment on independent.co.uk
--+---
 Reporter:  mwolfe|  Owner:  tbb-team
 Type:  defect| Status:  needs_information
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---
Changes (by cypherpunks):

 * status:  new => needs_information


Comment:

 I wanted to test this but the site is bloated like no tomorrow xD

 What I can suggest you to try to diagnose the issue:

 1. Open the Browser Console using `Ctrl+Shift+J` and see if any error pops
 up when you try to comment.
 2. Click on the HTTPS Everywhere icon and select "Block all unencrypted
 requests", then refresh the page where you want to comment and see if it's
 fixing thing.

--
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] #25319 [Core Tor/Tor]: commit 4438ef32 breaks tor macOS cross builds

[Tor Bug Tracker & Wiki]

#25319: commit 4438ef32 breaks tor macOS cross builds
--+
 Reporter:  gk|  Owner:  nickm
 Type:  defect| Status:  accepted
 Priority:  Medium|  Milestone:  Tor: 0.3.4.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  macos |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by nickm):

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


--
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] #22346 [Metrics/Statistics]: Investigate drop in Tor Browser update pings in early 2017 and 2018

[Tor Bug Tracker & Wiki]

#22346: Investigate drop in Tor Browser update pings in early 2017 and 2018
+--
 Reporter:  cypherpunks |  Owner:  metrics-team
 Type:  defect  | Status:  new
 Priority:  Medium  |  Milestone:
Component:  Metrics/Statistics  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by mcs):

 * cc: brade, mcs (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] #25313 [Core Tor/Tor]: Sandbox: Caught a bad syscall attempt (syscall poll)

[Tor Bug Tracker & Wiki]

#25313: Sandbox: Caught a bad syscall attempt (syscall poll)
--+
 Reporter:  cypherpunks   |  Owner:  nickm
 Type:  defect| Status:  accepted
 Priority:  Medium|  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  sandbox   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by nickm):

 * owner:  (none) => nickm
 * status:  new => accepted
 * keywords:   => sandbox
 * milestone:   => Tor: 0.3.3.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] #25306 [Core Tor/Tor]: tor_assertion_failed_(): Bug: ../src/or/hs_service.c:1985: rotate_all_descriptors: Assertion service->desc_current failed; aborting.

[Tor Bug Tracker & Wiki]

#25306: tor_assertion_failed_(): Bug: ../src/or/hs_service.c:1985:
rotate_all_descriptors: Assertion service->desc_current failed; aborting.
+--
 Reporter:  cypherpunks |  Owner:  (none)
 Type:  defect  | Status:  new
 Priority:  Medium  |  Milestone:  Tor:
|  0.3.3.x-final
Component:  Core Tor/Tor|Version:  Tor:
|  0.3.3.2-alpha
 Severity:  Normal  | Resolution:
 Keywords:  tor-hs crash 033-must 032-backport  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by nickm):

 * cc: dgoulet, asn (added)
 * keywords:   => tor-hs crash 033-must 032-backport


--
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] #23136 [Applications/Tor Launcher]: moat integration (fetch bridges for the user)

[Tor Bug Tracker & Wiki]

#23136: moat integration (fetch bridges for the user)
---+--
 Reporter:  mcs|  Owner:  brade
 Type:  defect | Status:  needs_review
 Priority:  Very High  |  Milestone:
Component:  Applications/Tor Launcher  |Version:
 Severity:  Normal | Resolution:
 Keywords:  TorBrowserTeam201802R  |  Actual Points:
Parent ID:  #24689 | Points:
 Reviewer: |Sponsor:  Sponsor4
---+--

Comment (by gk):

 Suppose I am starting Tor Browser, check the "Request another bridge"
 option, press Cancel (to think a bit more about it or for whatever reason)
 but click on the "Request a bridge" button pretty shortly thereafter I get
 greeted with
 {{{
 Tor Browser is already running, but is not responding. To open a new
 window, you must first close the existing Tor Browser process, or restart
 your system.
 }}}
 and I get an error about meek and handshake failure. That alone is pretty
 confusing for a number of reasons ("Hey, I don't want to open a new
 window, I want to get bridges!1!!" "Why the heck should I need to restart
 my system here just because I want to get bridges??" etc.), especially as
 I see the CAPTCHA in the background showing up. What's much worse, though,
 once this happens is that I can't get a single new bridge that way without
 restarting my browser session. I always get that error (and during the
 whole time my computer is pretty busy).

 I think we should try to handle this case more gracefully. Ideally, I
 think meek would be shut down again if I clicked the `Cancel` button
 (assuming that's not happening at the moment and the underlying issue).

--
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] #22346 [Metrics/Statistics]: Investigate drop in Tor Browser update pings in early 2017 and 2018

[Tor Bug Tracker & Wiki]

#22346: Investigate drop in Tor Browser update pings in early 2017 and 2018
+--
 Reporter:  cypherpunks |  Owner:  metrics-team
 Type:  defect  | Status:  new
 Priority:  Medium  |  Milestone:
Component:  Metrics/Statistics  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--

Comment (by boklm):

 Replying to [comment:8 karsten]:

 >
 > Would you want to play with the database yourself?  It's ~3G
 uncompressed, so it shouldn't be that hard to dump and compress it.  You'd
 have to create a local PostgreSQL database and import that file, and then
 you could run requests like this yourself.  (I'd still be around to help
 with the schema as needed!)

 Yes, if you can send me a dump of this database, I will look more closely
 at the numbers from the drop around 2018-01-24 to try to understand 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] #25320 [Internal Services/Service - jenkins]: Add CI builders to oniongit

[Tor Bug Tracker & Wiki]

#25320: Add CI builders to oniongit
-+-
 Reporter:  teor |  Owner:  hiro
 Type:  task | Status:
 |  assigned
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service - jenkins  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by hiro):

 Hi Teor,

 CI on gitlab is provided through what they calle runners
 (https://docs.gitlab.com/runner/). A runner can run jobs locally, through
 docker images or through ssh connections.
 Runners need to be registered with the gitlab instance through a token.
 Once a runner is registered it can be assigned to projects or be shared by
 all projects.
 I do not have a VM available to run a specific architecture at the moment,
 but I'd be happy to help you hook up resources to oniongit.
 We could also think to make some VM w/ specific architecture requirements
 if we wanted, but we would need the actual hardware where we can run
 those.

--
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] [Tor Bug Tracker & Wiki] Batch modify: #25055, #25316

[Tor Bug Tracker & Wiki]

Batch modification to #25055, #25316 by nickm:


Comment:
s/must-033/033-must/

--
Tickets 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] #25308 [Core Tor]: Onion service node pinning by default

[Tor Bug Tracker & Wiki]

#25308: Onion service node pinning by default
-+--
 Reporter:  cypherpunks  |  Owner:  (none)
 Type:  enhancement  | Status:  reopened
 Priority:  Medium   |  Milestone:
Component:  Core Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by adrelanos):

 * cc: adrelanos@… (added)
 * status:  closed => reopened
 * component:  - Select a component => Core Tor
 * 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] #25333 [Core Tor/Tor]: NOT SECURE CONECTION please help

[Tor Bug Tracker & Wiki]

#25333: NOT SECURE CONECTION please help
-+---
 Reporter:  kiokawasaki1998  |  Owner:  (none)
 Type:  defect   | Status:  needs_information
 Priority:  Medium   |  Milestone:
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+---

Comment (by kiokawasaki1998):

 browser writes  secure conection failed

--
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] #25333 [Core Tor/Tor]: NOT SECURE CONECTION please help

[Tor Bug Tracker & Wiki]

#25333: NOT SECURE CONECTION please help
-+---
 Reporter:  kiokawasaki1998  |  Owner:  (none)
 Type:  defect   | Status:  needs_information
 Priority:  Medium   |  Milestone:
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+---

Comment (by kiokawasaki1998):

 tor browser 7.5

--
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] #25333 [Core Tor/Tor]: NOT SECURE CONECTION please help

[Tor Bug Tracker & Wiki]

#25333: NOT SECURE CONECTION please help
-+---
 Reporter:  kiokawasaki1998  |  Owner:  (none)
 Type:  defect   | Status:  needs_information
 Priority:  Medium   |  Milestone:
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+---

Comment (by kiokawasaki1998):

 thanks for support

--
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] #25112 [Applications/Tor Browser]: Tor Browser 7.5 is not working on Windows Vista 64bit

[Tor Bug Tracker & Wiki]

#25112: Tor Browser 7.5 is not working on Windows Vista 64bit
-+-
 Reporter:  gk   |  Owner:
 |  pospeselr
 Type:  defect   | Status:
 |  needs_information
 Priority:  High |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Major| Resolution:
 Keywords:  ff60-esr-will-have,  |  Actual Points:
  TorBrowserTeam201802   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by cypherpunks):

 * status:  assigned => needs_information


Comment:

 Replying to [comment:11 pospeselr]:
 > This failure happens due to a missing wow_helper.exe in the TBB package.
 They didn't tell you?
 > Everything works just fine when I copy over the version packaged with
 latest Firefox.
 What do you mean? It was removed as part of removing support for Vista.
 > Currently investigating why this exe isn't being built or packaged.
 The same way why helper.exe isn't being built, and then they wonder why
 staged updates don't work.
 > An interesting sidenote, the latest Chromium sandbox code no longer uses
 wow_helper.exe.  Seems like it was removed in Chromium commit
 1812d0d777dbe2162e88f6a0a205c8b483008626 as part of removing support for
 XP and Vista.
 It was needed for Vista only.

--
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] #25333 [Core Tor/Tor]: NOT SECURE CONECTION please help

[Tor Bug Tracker & Wiki]

#25333: NOT SECURE CONECTION please help
-+---
 Reporter:  kiokawasaki1998  |  Owner:  (none)
 Type:  defect   | Status:  needs_information
 Priority:  Medium   |  Milestone:
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+---

Comment (by kiokawasaki1998):

 please help

--
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] #25333 [Core Tor/Tor]: NOT SECURE CONECTION please help

[Tor Bug Tracker & Wiki]

#25333: NOT SECURE CONECTION please help
-+---
 Reporter:  kiokawasaki1998  |  Owner:  (none)
 Type:  defect   | Status:  needs_information
 Priority:  Medium   |  Milestone:
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+---

Comment (by kiokawasaki1998):

 i cant conect to duckduck i cant make nothing

--
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] #25333 [Core Tor/Tor]: NOT SECURE CONECTION please help

[Tor Bug Tracker & Wiki]

#25333: NOT SECURE CONECTION please help
-+---
 Reporter:  kiokawasaki1998  |  Owner:  (none)
 Type:  defect   | Status:  needs_information
 Priority:  Medium   |  Milestone:
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+---

Comment (by kiokawasaki1998):

 tor writes that conection isnt secure

--
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] #25329 [Metrics/Library]: Enable metrics-lib to process large (> 2G) logfiles

[Tor Bug Tracker & Wiki]

#25329: Enable metrics-lib to process large (> 2G) logfiles
-+--
 Reporter:  iwakeh   |  Owner:  iwakeh
 Type:  enhancement  | Status:  accepted
 Priority:  Very High|  Milestone:
Component:  Metrics/Library  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:  #25317   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by iwakeh):

 * status:  needs_information => accepted


Comment:

 Replying to [comment:3 karsten]:
 > And the reason to have `getRawDescriptorBytes()` return ''compressed''
 raw descriptor bytes is that it has to return ''something'', as it's
 overridden from `Descriptor`?

 Exactly!

 >
 > If so, works for me.
 >
 > If you make this change, please look out for surrounding comments that
 need changing. Thanks!

 Sure.

--
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] #25333 [Core Tor/Tor]: NOT SECURE CONECTION please help

[Tor Bug Tracker & Wiki]

#25333: NOT SECURE CONECTION please help
-+---
 Reporter:  kiokawasaki1998  |  Owner:  (none)
 Type:  defect   | Status:  needs_information
 Priority:  Medium   |  Milestone:
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+---

Comment (by kiokawasaki1998):

 i try to uninstal browser and download new one but doesnt work

--
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] [Tor Bug Tracker & Wiki] Batch modify: #22059, #24796, #18864, #19076, ...

[Tor Bug Tracker & Wiki]

Batch modification to #22059, #24796, #18864, #19076, #19077, #21863, #22170, 
#22171, #24919, #24920, #24926, #24957, #25164 by sysrqb:
parent to #5709

Comment:
Moving these to #5709, these aren't blockers anymore. We'll merge Orfox patches 
first, then audit everything as we move to m-c and work on TBA. (We should 
create more tickets as we find more items that need investigating/fixing)

--
Tickets 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] #25333 [- Select a component]: NOT SECURE CONECTION please help

[Tor Bug Tracker & Wiki]

#25333: NOT SECURE CONECTION please help
--+
 Reporter:  kiokawasaki1998   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 2/22/2018 8:47:13 AM.900 [NOTICE] Disablenetwork is set.Tor will not make
 or accept non-control network conections.shutting down all exosting
 connections.
 2/22/2018 8:47:13 AM.900 [NOTICE] Opening Socks listener on 127.0.0.1:9150
 2/22/2018 8:47:13 AM.300 [NOTICE] bootsraped 80% conecting to the Tor
 network
 2/22/2018 8:47:13 AM.300 [NOTICE] bootsraped 85% finishing handshake with
 first hop
 2/22/2018 8:47:13 AM.300 [NOTICE] Bridge 'nx01' has both an IPV6
 adress.will prefer using its IPV4 addreses(85.17.30.79:443) based in
 configured Bridge address.
 2/22/2018 8:47:13 AM.400 [WARN] Proxy Client:unable to connect to
 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 (''general socks server
 failure'')
 2/22/2018 8:47:13 AM.200 [WARN] Proxy Client:unable to connect to
 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 (''general socks server
 failure'')
 2/22/2018 8:47:13 AM.300 [NOTICE] Bootsrapped 90:Establishing a Tor
 circuit
 2/22/2018 8:47:13 AM.500 [NOTICE]new bridge descriptor 'dragon' (fresh
 )$D9A82D2F9C2F65A18407B1D2B76F130847F8B5D-dragon at 37.218.245.14
 2/22/2018 8:47:13 AM.600 [NOTICE]new bridge descriptor 'ndnop5' (fresh) :
 $BBB28DF0F201E706BE564EFE690FE9577DD836D-ndnop5 at 109.105.109.147

--
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] #25333 [Core Tor/Tor]: NOT SECURE CONECTION please help

[Tor Bug Tracker & Wiki]

#25333: NOT SECURE CONECTION please help
-+---
 Reporter:  kiokawasaki1998  |  Owner:  (none)
 Type:  defect   | Status:  needs_information
 Priority:  Medium   |  Milestone:
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+---

Comment (by kiokawasaki1998):

 the problem os unsecure conection when i opern tor browser start page
 where i can check my conection page doesnt load

--
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] #25333 [Core Tor/Tor]: NOT SECURE CONECTION please help

[Tor Bug Tracker & Wiki]

#25333: NOT SECURE CONECTION please help
-+---
 Reporter:  kiokawasaki1998  |  Owner:  (none)
 Type:  defect   | Status:  needs_information
 Priority:  Medium   |  Milestone:
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+---
Changes (by teor):

 * status:  new => needs_information
 * component:  - Select a component => Core Tor/Tor


Comment:

 Hi, can you help us understand what the problem is?

--
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] #25315 [Applications/Tor Browser]: Web sites embedding https://www.facebook.com/tr/ freeze Tor Browser due to NoScript's XSS filter

[Tor Bug Tracker & Wiki]

#25315: Web sites embedding https://www.facebook.com/tr/ freeze Tor Browser due 
to
NoScript's XSS filter
--+
 Reporter:  gk|  Owner:  tbb-team
 Type:  defect| Status:  closed
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Major | Resolution:  worksforme
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by gk):

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


Comment:

 Seems to work for me 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] #23635 [Core Tor/Tor]: improve AccountingStart manual entry

[Tor Bug Tracker & Wiki]

#23635: improve AccountingStart manual entry
+--
 Reporter:  cypherpunks |  Owner:  (none)
 Type:  enhancement | Status:  needs_revision
 Priority:  Medium  |  Milestone:  Tor:
|  0.3.3.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  easy, doc, review-group-33  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  dgoulet |Sponsor:
+--
Changes (by dgoulet):

 * status:  needs_review => needs_revision


Comment:

 {{{
 +[...] The relay will go at full speed,
 +use all the quota you specify, then hibernate for the rest of the
 month.(The
 +day must be between 1 and 28.)
 }}}

 Isn't "for the rest of the accounting period" ?

 Also, a white space after the sentence would be nice so the `(The` is
 properly spaced.

--
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] #25326 [Applications/Tor Browser]: connesisone sicura non riuscita

[Tor Bug Tracker & Wiki]

#25326: connesisone sicura non riuscita
--+--
 Reporter:  Toruser85 |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:  Tor: unspecified
 Severity:  Major | Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by Toruser85):

 * Attachment "SenzaTitolo.pdf" added.

 schermata errore

--
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] #25326 [Applications/Tor Browser]: connesisone sicura non riuscita

[Tor Bug Tracker & Wiki]

#25326: connesisone sicura non riuscita
--+--
 Reporter:  Toruser85 |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:  Tor: unspecified
 Severity:  Major |   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 dopo l'avvio qualunque ricerca, pagine web o aggiornamento io cerchi di
 fare mi compare errore connesione sicura non riuscita. Di punto in bianco
 senza che nulla sia stato modificato la settimana scorsa funzionava alla
 perfezione

--
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] #25310 [Core Tor/Tor]: Document our policy for Rust dependencies

[Tor Bug Tracker & Wiki]

#25310: Document our policy for Rust dependencies
---+
 Reporter:  isis   |  Owner:  (none)
 Type:  enhancement| Status:  new
 Priority:  Medium |  Milestone:  Tor: 0.3.4.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  rust, tor-doc  |  Actual Points:
Parent ID: | Points:  1
 Reviewer: |Sponsor:  SponsorM
---+

Comment (by nickm):

 Also we should probably figure out what our plans are for keeping our
 dependencies up-to-date.

--
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] #25325 [- Select a component]: Secure Connection Failed

[Tor Bug Tracker & Wiki]

#25325: Secure Connection Failed
--+
 Reporter:  ATOMShadow|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 Secure Connection Failed

 The connection to the server was reset while the page was loading.

 The page you are trying to view cannot be shown because the
 authenticity of the received data could not be verified.
 Please contact the website owners to inform them of this problem.

 i got this problem recently and i dont know how to fix it can someone help
 me ?

 thats in the torlog 2/21/2018 16:39:13 PM.200 [NOTICE] Bootstrapped 85%:
 Finishing handshake with first hop
 2/21/2018 16:39:13 PM.200 [NOTICE] Bootstrapped 90%: Establishing a Tor
 circuit
 2/21/2018 16:39:13 PM.600 [NOTICE] Tor has successfully opened a circuit.
 Looks like client functionality is working.
 2/21/2018 16:39:13 PM.600 [NOTICE] Bootstrapped 100%: Done
 2/21/2018 16:39:15 PM.900 [NOTICE] New control connection opened from
 127.0.0.1.
 2/21/2018 16:39:16 PM.200 [NOTICE] New control connection opened from
 127.0.0.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] #25323 [Core Tor/Tor]: Create an official tor-rust-dependencies.git repository

[Tor Bug Tracker & Wiki]

#25323: Create an official tor-rust-dependencies.git repository
--+
 Reporter:  nickm |  Owner:  nickm
 Type:  task  | Status:  closed
 Priority:  Medium|  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:  implemented
 Keywords:  rust build|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by nickm):

 * status:  assigned => closed
 * resolution:   => implemented


Comment:

 This is done now.

--
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] #25324 [Core Tor/Tor]: Create a tor-releases.git repository.

[Tor Bug Tracker & Wiki]

#25324: Create a tor-releases.git repository.
--+
 Reporter:  nickm |  Owner:  (none)
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 This repository should be a fork of the main Tor repository, containing
 only the releases.  In particular, it should have:

  * All supported tagged releases.
  * "release-0.x.y" branches that are updated whenever a release is tagged,
 and not otherwise.
  * "stable", "oldstable", "lts", and "alpha" branches that are updated
 whenever a release is tagged, and not otherwise.  These branches may be
 force-pushed.
  * A "master" branch containing only a README file that tells you what
 branches to really use.

 For background, see https://www.mail-archive.com/tor-
 d...@lists.torproject.org/msg10246.html and the surrounding thread.

 We should also update doc/HACKING/ReleasingTor.md to describe this
 process.

--
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] #25323 [Core Tor/Tor]: Create an official tor-rust-dependencies.git repository

[Tor Bug Tracker & Wiki]

#25323: Create an official tor-rust-dependencies.git repository
--+
 Reporter:  nickm |  Owner:  nickm
 Type:  task  | Status:  assigned
 Priority:  Medium|  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal|   Keywords:  rust build
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 Right now, our tor-rust-dependencies repository lives in Sebastian's
 namespace.  We should turn it into an official repository in the root
 namespace, and adjust our submodules config and our documentation
 accordingly.

 We should also figure out what our plan is for keeping the dependencies in
 it up-to-date.

--
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] #16472 [Applications/Tor Browser]: Upgrade Binutils to 2.25+ for Tor Browser builds

[Tor Bug Tracker & Wiki]

#16472: Upgrade Binutils to 2.25+ for Tor Browser builds
--+--
 Reporter:  gk|  Owner:  tbb-team
 Type:  task  | Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-rbm, boklm201802  |  Actual Points:
Parent ID:  #12968| Points:
 Reviewer:|Sponsor:
--+--

Comment (by boklm):

 Replying to [comment:20 gk]:
 > boklm: We are using an older tag for selfrando. Could you double-check
 that the issue is still there with the latest code on `master`? That said
 I think it is fine dropping selfrando in a separate patch for this bug if
 that's the only issue blocking the binutils uprade, at least until it is
 fixed upstream (i.e. on selfrando's side).

 I tried a build using selfrando commit
 de95c99364214d631df01364e0e87e6b6c307eba (current master), and it also
 fails with the error from comment:9.

--
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] #25324 [Core Tor/Tor]: Create a tor-releases.git repository.

[Tor Bug Tracker & Wiki]

#25324: Create a tor-releases.git repository.
--+
 Reporter:  nickm |  Owner:  (none)
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by nickm):

 Alternatively, we could do this with more branches in the tor.git
 repository.  We would need to mark the semantic branches (alpha, stable,
 lts)  as "okay to force-push".

--
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] #25325 [- Select a component]: Secure Connection Failed

[Tor Bug Tracker & Wiki]

#25325: Secure Connection Failed
--+
 Reporter:  ATOMShadow|  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:
--+

Comment (by cypherpunks):

 Well you choose a new circuit for that website but that one has currently
 a bug in these situations... So this ticket is a duplicate it seems?

--
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] #20892 [Applications/Tor Browser]: tools/update-responses/download_missing_versions fails to download OSX mar files

[Tor Bug Tracker & Wiki]

#20892: tools/update-responses/download_missing_versions fails to download OSX 
mar
files
--+--
 Reporter:  boklm |  Owner:  tbb-team
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:  TorBrowserTeam201802R |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by gk):

 * status:  needs_review => closed
 * resolution:   => 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] #25275 [Internal Services/Service - git]: Please delete tag collector-1.5.0 in collector.git

[Tor Bug Tracker & Wiki]

#25275: Please delete tag collector-1.5.0 in collector.git
-+-
 Reporter:  karsten  |  Owner:  tor-gitadm
 Type:  task | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service - git  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by hiro):

 * status:  new => needs_revision


Comment:

 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

[tor-bugs] #25321 [- Select a component]: Unable to comment on independent.co.uk

[Tor Bug Tracker & Wiki]

#25321: Unable to comment on independent.co.uk
--+
 Reporter:  mwolfe|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 Until a week or two ago (I don't comment every day, so it might have been
 a month ago) I was able to comment on the independent.co.uk news site. Now
 I cannot comment with Tor (I don't want anyone to know who is making my
 comments).

 Am I doing something wrong? Before, I wrote in, and the problem was that
 comments were insecure, while the news articles were https secure, and I
 learned how to disable that protection. Now I cannot log in at all.

 I have no idea if the Independent is blocking all comments from Tor users
 as part of its firewall, or if Tor has some protection against the kind of
 stuff they try to extract from commentators.

 Any help or advice would be appreciated.

--
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] #22346 [Metrics/Statistics]: Investigate drop in Tor Browser update pings in early 2017 and 2018 (was: Investigate drop in Tor Browser update pings in early 2017, possibly caused by upd

[Tor Bug Tracker & Wiki]

#22346: Investigate drop in Tor Browser update pings in early 2017 and 2018
+--
 Reporter:  cypherpunks |  Owner:  metrics-team
 Type:  defect  | Status:  new
 Priority:  Medium  |  Milestone:
Component:  Metrics/Statistics  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--

Comment (by gk):

 Interestingly it seems this is happening again with a X.5 release. It
 seems we need a better theory assuming both incidents can be explained by
 the same underlying cause.

--
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] #25322 [Internal Services/Tor Sysadmin Team]: Finding a way to serve search.tpo for the different portals

[Tor Bug Tracker & Wiki]

#25322: Finding a way to serve search.tpo for the different portals
-+-
 Reporter:  hiro |  Owner:  tpa
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 Hi,

 I have a machine that will be serving search results for the coming web
 portals.
 This is a Solr installation + a pyramid app to display the search results
 in html.

 This machine lives on 195.201.2.191.

 Since the portals are static html pages, I am trying to think of a way so
 that at the local url '/search' we can serve the search result of the
 search service.

 So for example support.torproject.org/search would display the search
 results for the support portal from 195.201.2.191.

 Now there are a few issues that we should consider.

 1. Onion service
 The search service will be behind its own onion service.

 2. Could we just offer a redirect through htaccess?

 3. should we have a search.tpo service and that's it?

 Points 2. and 3. could be complicated in terms of user experience. I'd say
 that if a user search something they do not necessarly expect to be taken
 to a different window or different page.

 Any other ideas are welcomed.

--
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] #25316 [Core Tor/Tor]: Assertion failure in scale_active_circuits

[Tor Bug Tracker & Wiki]

#25316: Assertion failure in scale_active_circuits
-+
 Reporter:  Logforme |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  High |  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor |Version:  Tor: 0.3.2.9
 Severity:  Major| Resolution:
 Keywords:  crash, must-033  |  Actual Points:
Parent ID:   | Points:  0.5
 Reviewer:   |Sponsor:
-+

Comment (by dgoulet):

 Fun one...

 I can only see this assert() being triggered if we added twice the same
 ewma circ policy to the active circuit queue. So in the loop, the first
 pass would change the `last_adjusted_tick` and the second pass, the assert
 would be triggered. The only way to do that would be to have called
 `notify_circ_active()` on an already active circuit for which I can't find
 a way how that would be possible

 We can't have an entry `last_adjusted_tick` in the policy active circuit
 pqueue that wasn't synchronized with the
 `active_circuit_pqueue_last_recalibrated` value. This is done in
 `add_cell_ewma()` which adds the ewma circuit data to the active list and
 just before does:

 {{{
 last_adjusted_tick = active_circuit_pqueue_last_recalibrated
 }}}

 We can't end up in `scale_active_circuits()` for a circuit that is *not*
 in the active queue because of the assert at the end of
 `ewma_notify_xmit_cells()` which makes sure that we've xmit a cell on a
 active circuit of the policy:

 {{{
   tmp = pop_first_cell_ewma(pol);
   tor_assert(tmp == cell_ewma);
   add_cell_ewma(pol, cell_ewma);
 }}}

 Confusing.

--
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] #25013 [Applications/Tor Browser]: Move TorButton code to the tor browser repository

[Tor Bug Tracker & Wiki]

#25013: Move TorButton code to the tor browser repository
--+
 Reporter:  igt0  |  Owner:  tbb-team
 Type:  defect| Status:  needs_revision
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  TorBrowserTeam201802  |  Actual Points:
Parent ID:  #24855| Points:
 Reviewer:  gk, sysrqb, mcs,  |Sponsor:
--+

Comment (by gk):

 FWIW: I can see us copying over files from the Torbutton repo or just
 package up an .xpi and put the extracted files into tor-browser.git before
 we tag (and use the machinery developed in some of the patches above). I
 just think that step 1 of the migration should not contain getting rid of
 the Torbutton repo. We should do this once we integrate the components we
 need tighter into the browser. I guess this would be a thing, at some
 point, for step 3 in Arthur's staged approach.

--
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] #24689 [Applications/Tor Browser]: deliver Moat feature to end-users [tracking bug]

[Tor Bug Tracker & Wiki]

#24689: deliver Moat feature to end-users [tracking bug]
--+--
 Reporter:  mcs   |  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:  Sponsor4
--+--
Changes (by anonym):

 * cc: anonym (added)


Comment:

 Is Moat planned to be included in the stable Tor Browser release based on
 Firefox 52.7 on 2018-03-13? Otherwise, what is your best best? I am asking
 since there's some work needed on Tails' side (e.g. clearnet DNS
 resolution which otherwise is completely blocked) so we need to
 coordinate.

--
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] #24689 [Applications/Tor Browser]: deliver Moat feature to end-users [tracking bug]

[Tor Bug Tracker & Wiki]

#24689: deliver Moat feature to end-users [tracking bug]
--+--
 Reporter:  mcs   |  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:  Sponsor4
--+--

Comment (by gk):

 Replying to [comment:1 anonym]:
 > Is Moat planned to be included in the stable Tor Browser release based
 on Firefox 52.7 on 2018-03-13? Otherwise, what is your best best? I am
 asking since there's some work needed on Tails' side (e.g. clearnet DNS
 resolution which otherwise is completely blocked) so we need to
 coordinate.

 No, in the related alpha bundles. Moat is a big feature so I am not sure
 about backporting it to the 7.5 series. It's currently not planned at
 least. I estimate it will be available in Tor Browser 8.0 which is
 supposed to get out at the end of August.

--
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] #25320 [Internal Services/Service - jenkins]: Add CI builders to oniongit

[Tor Bug Tracker & Wiki]

#25320: Add CI builders to oniongit
-+
 Reporter:  teor |  Owner:  weasel
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service - jenkins  |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+
 I'd like to be able to build and run unit tests on my branches on oniongit
 with:
 * tor pure C
 * tor Rust/C
 On:
 * i386
 * x86_64/amd64
 * armhf
 * arm64

 There doesn't seem to be an oniongit component, but I think this involves
 Jenkins, too.

--
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] #25126 [Applications/Tor Browser]: about:tor should work on small screens (mobile)

[Tor Bug Tracker & Wiki]

#25126: about:tor should work on small screens (mobile)
+--
 Reporter:  igt0|  Owner:  tbb-team
 Type:  enhancement | Status:
|  needs_revision
 Priority:  Medium  |  Milestone:
Component:  Applications/Tor Browser|Version:
 Severity:  Normal  | Resolution:
 Keywords:  tbb-torbutton,TorBrowserTeam201802  |  Actual Points:
Parent ID:  #24855  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by gk):

 * status:  needs_review => needs_revision
 * keywords:  tbb-torbutton,TorBrowserTeam201802R => tbb-
 torbutton,TorBrowserTeam201802


Comment:

 Marking this as `needs_revision` as the #25013 needs to get revised as
 well.

--
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] #25161 [Metrics/CollecTor]: Fix any memory problem caused by number of log files to be imported by the webstats module

[Tor Bug Tracker & Wiki]

#25161: Fix any memory problem caused by number of log files to be imported by 
the
webstats module
---+---
 Reporter:  karsten|  Owner:  iwakeh
 Type:  defect | Status:  needs_information
 Priority:  Medium |  Milestone:
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---

Comment (by iwakeh):

 JConsole does also connect remotely; see
 
[https://docs.oracle.com/javase/8/docs/technotes/guides/management/jconsole.html
 JConsole] and
 
[https://docs.oracle.com/javase/8/docs/technotes/guides/management/agent.html#gdenl
 remote management setup].  In a local network, where I suppose you run the
 import in, that should be fine.

--
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] #25320 [Internal Services/Service - jenkins]: Add CI builders to oniongit

[Tor Bug Tracker & Wiki]

#25320: Add CI builders to oniongit
-+-
 Reporter:  teor |  Owner:  hiro
 Type:  task | Status:
 |  assigned
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service - jenkins  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by hiro):

 * status:  new => assigned
 * owner:  weasel => hiro


--
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] #25161 [Metrics/CollecTor]: Fix any memory problem caused by number of log files to be imported by the webstats module

[Tor Bug Tracker & Wiki]

#25161: Fix any memory problem caused by number of log files to be imported by 
the
webstats module
---+---
 Reporter:  karsten|  Owner:  iwakeh
 Type:  defect | Status:  needs_information
 Priority:  Medium |  Milestone:
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---

Comment (by karsten):

 Alright, going with top then. It's running on a headless machine, so
 jconsole/jvisualvm are not available, at least not easily. Started.

--
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] #25319 [Core Tor/Tor]: commit 4438ef3288256e1f1ba706c157206a2ac190781d breaks tor macOS cross builds

[Tor Bug Tracker & Wiki]

#25319: commit 4438ef3288256e1f1ba706c157206a2ac190781d breaks tor macOS cross
builds
--+
 Reporter:  gk|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.3.4.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 The macOS cross build we do for Tor Browser is broken after removing a
 bunch of redundant #includes (i.e.
 4438ef3288256e1f1ba706c157206a2ac190781d):
 {{{
   CC   src/test/src_test_test-test_address_set.o
 In file included from src/test/test_address.c:15:
 /var/tmp/dist/macosx-toolchain/SDK//usr/include/net/if.h:300:19: error:
 field has incomplete type 'struct sockaddr'
 struct  sockaddr ifru_addr;
  ^
 /var/tmp/dist/macosx-toolchain/SDK//usr/include/net/if.h:300:10: note:
 forward declaration of 'struct sockaddr'
 struct  sockaddr ifru_addr;
 ^
 /var/tmp/dist/macosx-toolchain/SDK//usr/include/net/if.h:301:19: error:
 field has incomplete type 'struct sockaddr'
 struct  sockaddr ifru_dstaddr;
  ^
 /var/tmp/dist/macosx-toolchain/SDK//usr/include/net/if.h:300:10: note:
 forward declaration of 'struct sockaddr'
 struct  sockaddr ifru_addr;
 ^
 /var/tmp/dist/macosx-toolchain/SDK//usr/include/net/if.h:302:19: error:
 field has incomplete type 'struct sockaddr'
 struct  sockaddr ifru_broadaddr;
  ^
 /var/tmp/dist/macosx-toolchain/SDK//usr/include/net/if.h:300:10: note:
 forward declaration of 'struct sockaddr'
 struct  sockaddr ifru_addr;
 ^
 /var/tmp/dist/macosx-toolchain/SDK//usr/include/net/if.h:346:18: error:
 field has incomplete type 'struct sockaddr'
 struct  sockaddr ifra_addr;
  ^
 /var/tmp/dist/macosx-toolchain/SDK//usr/include/net/if.h:300:10: note:
 forward declaration of 'struct sockaddr'
 struct  sockaddr ifru_addr;
 ^
 /var/tmp/dist/macosx-toolchain/SDK//usr/include/net/if.h:347:18: error:
 field has incomplete type 'struct sockaddr'
 struct  sockaddr ifra_broadaddr;
  ^
 /var/tmp/dist/macosx-toolchain/SDK//usr/include/net/if.h:300:10: note:
 forward declaration of 'struct sockaddr'
 struct  sockaddr ifru_addr;
 ^
 /var/tmp/dist/macosx-toolchain/SDK//usr/include/net/if.h:348:18: error:
 field has incomplete type 'struct sockaddr'
 struct  sockaddr ifra_mask;
  ^
 /var/tmp/dist/macosx-toolchain/SDK//usr/include/net/if.h:300:10: note:
 forward declaration of 'struct sockaddr'
 struct  sockaddr ifru_addr;
 ^
 /var/tmp/dist/macosx-toolchain/SDK//usr/include/net/if.h:431:26: error:
 field has incomplete type 'struct sockaddr_storage'
 struct sockaddr_storage addr;   /* in/out */
 ^
 /var/tmp/dist/macosx-toolchain/SDK//usr/include/net/if.h:431:9: note:
 forward declaration of 'struct sockaddr_storage'
 struct sockaddr_storage addr;   /* in/out */
^
 /var/tmp/dist/macosx-toolchain/SDK//usr/include/net/if.h:432:26: error:
 field has incomplete type 'struct sockaddr_storage'
 struct sockaddr_storage dstaddr; /* out */
 ^
 /var/tmp/dist/macosx-toolchain/SDK//usr/include/net/if.h:431:9: note:
 forward declaration of 'struct sockaddr_storage'
 struct sockaddr_storage addr;   /* in/out */
^
 8 errors generated.
 Makefile:9761: recipe for target 'src/test/src_test_test-test_address.o'
 failed
 make[1]: *** [src/test/src_test_test-test_address.o] Error 1
 make[1]: *** Waiting for unfinished jobs
 make[1]: Leaving directory '/var/tmp/build/tor-master'
 make: *** [all] Error 2
 Makefile:3394: recipe for target 'all' failed
 }}}

--
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] #25319 [Core Tor/Tor]: commit 4438ef32 breaks tor macOS cross builds (was: commit 4438ef3288256e1f1ba706c157206a2ac190781d breaks tor macOS cross builds)

[Tor Bug Tracker & Wiki]

#25319: commit 4438ef32 breaks tor macOS cross builds
--+
 Reporter:  gk|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.3.4.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  macos |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by teor):

 * keywords:   => macos


Comment:

 There is no ticket for this commit.

 Maybe there is a bug in our configure header detection, or maybe the
 headers really do need to be included in that order.

 The compat.c change may also be problematic, because it's conditional on
 __APPLE__.

--
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] #25275 [Internal Services/Service - git]: Please delete tag collector-1.5.0 in collector.git

[Tor Bug Tracker & Wiki]

#25275: Please delete tag collector-1.5.0 in collector.git
-+
 Reporter:  karsten  |  Owner:  tor-gitadm
 Type:  task | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service - git  |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+
Changes (by teor):

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


Comment:

 I think this was actually 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] #16472 [Applications/Tor Browser]: Upgrade Binutils to 2.25+ for Tor Browser builds

[Tor Bug Tracker & Wiki]

#16472: Upgrade Binutils to 2.25+ for Tor Browser builds
--+--
 Reporter:  gk|  Owner:  tbb-team
 Type:  task  | Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-rbm, boklm201802  |  Actual Points:
Parent ID:  #12968| Points:
 Reviewer:|Sponsor:
--+--

Comment (by gk):

 boklm: We are using an older tag for selfrando. Could you double-check
 that the issue is still there with the latest code on `master`? That said
 I think it is fine dropping selfrando in a separate patch for this bug if
 that's the only issue blocking the binutils uprade, at least until it is
 fixed upstream (i.e. on selfrando's side).

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

Re: [tor-bugs] #25268 [Core Tor/Tor]: cmux: Remove round robin code and make EWMA mandatory

[Tor Bug Tracker & Wiki]

#25268: cmux: Remove round robin code and make EWMA mandatory
-+-
 Reporter:  dgoulet  |  Owner:  dgoulet
 Type:  enhancement  | Status:
 |  needs_review
 Priority:  Low  |  Milestone:  Tor:
 |  0.3.4.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-cmux, tor-sched, tor-relay,  |  Actual Points:
  tor-circuit, review-group-33   |
Parent ID:  #25328   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by dgoulet):

 * parent:   => #25328


--
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] [Tor Bug Tracker & Wiki] Batch modify: #6767, #24454, #25226, #25313, ...

[Tor Bug Tracker & Wiki]

Batch modification to #6767, #24454, #25226, #25313, #21969, #24759, #25208, 
#25213 by nickm:


Comment:
Mark some tickets as possibly belonging in 033-must.


--
Tickets 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] #22614 [Applications/Tor Browser]: Make e10s/non-e10s Tor Browsers indistinguishable

[Tor Bug Tracker & Wiki]

#22614: Make e10s/non-e10s Tor Browsers indistinguishable
-+-
 Reporter:  cypherpunks  |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  ff52-esr, tbb-fingerprinting,|  Actual Points:
  TorBrowserTeam201802R, tbb-no-uplift, ff60 |
  -esr-obsolete  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by cypherpunks):

 This ticket was filed to investigate the differences between modes, but
 closed as fixed without mentioning the results of it. What was found
 during RFP project?

 Replying to [comment:10 arthuredelstein]:
 > mcs mentioned this fix will no longer be needed in TBB/ESR60 because of
 the patches landed in https://bugzilla.mozilla.org/show_bug.cgi?id=981796
 Not comment:2?
 Does upstream team agree with your `ff60-esr-obsolete` or can prove `ff60
 -esr-will-have`?

--
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] #25328 [Core Tor/Tor]: cmux: Refactor, test and improve performance of the circuitmux subsystem

[Tor Bug Tracker & Wiki]

#25328: cmux: Refactor, test and improve performance of the circuitmux subsystem
+--
 Reporter:  dgoulet |  Owner:  dgoulet
 Type:  | Status:  assigned
  enhancement   |
 Priority:  Low |  Milestone:  Tor: 0.3.4.x-final
Component:  Core|Version:
  Tor/Tor   |
 Severity:  Normal  |   Keywords:  tor-cmux, tor-relay, refactoring
Actual Points:  |  Parent ID:
   Points:  |   Reviewer:
  Sponsor:  |
+--
 The cmux subsystem (`src/or/circuitmux.c`) is part of tor's fast path. It
 gets called at every cell or at every few cell and every new or dying
 circuit.

 It is currently in our top 5 of CPU hugger (see #25152) and also has a
 certain complexity to it. However, in practice, it should be quite simple.
 #25268 helps a lot by removing dead code and helping making the code more
 readable.

 In order to improve that subsystem, there are few steps that need to be
 taken before we can address something like #25152. Furthermore, in order
 to fix some things in the scheduler (#23993), this work should be done so
 we don't add more complexity to that code.

 Refactoring this subsystem to something more simple also will help testing
 it for which right now, it is virtually untested (see
 `src/test/test_circuitmux.c`).

 I'm taking this ticket because I do have planned out this work already and
 it might change over time.

--
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] #25329 [Metrics/Library]: Enable metrics-lib to process large (> 2G) logfiles

[Tor Bug Tracker & Wiki]

#25329: Enable metrics-lib to process large (> 2G) logfiles
-+---
 Reporter:  iwakeh   |  Owner:  iwakeh
 Type:  enhancement  | Status:  needs_information
 Priority:  Very High|  Milestone:
Component:  Metrics/Library  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:  #25317   | Points:
 Reviewer:   |Sponsor:
-+---
Changes (by iwakeh):

 * status:  accepted => needs_information


--
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] #25327 [Applications/Tor Browser]: debug files are not deterministic

[Tor Bug Tracker & Wiki]

#25327: debug files are not deterministic
-+-
 Reporter:  boklm|  Owner:  tbb-team
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor |Version:
  Browser|   Keywords:  TorBrowserTeam201802,
 Severity:  Normal   |  tbb-rbm
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 After fixing #24999, when building the 8.0a2 release we noticed that the
 *-debug.tar.gz files are not deterministic.

 It seems that the only difference is in the gzip timestamp, according to
 the diffoscope output:
 {{{
 --- tor-linux32-debug.tar.gz
 +++ ../alpha/unsigned/8.0a2-build2/tor-linux32-debug.tar.gz
 ├── metadata
 │ @@ -1 +1 @@
 │ -gzip compressed data, last modified: Wed Feb 21 12:09:06 2018, from
 Unix
 │ +gzip compressed data, last modified: Wed Feb 21 11:41:29 2018, from
 Unix
 }}}

 We can fix that by using the `-n` gzip flag:
 {{{
-n --no-name
   When compressing, do not save the original file name and
 time stamp
   by  default.  (The original name is always saved if the name
 had to
   be truncated.) When decompressing, do not restore the
 original file
   name  if  present  (remove only the gzip suffix from the
 compressed
   file name) and do not restore the original time  stamp  if
 present
   (copy it from the compressed file). This option is the
 default when
   decompressing.
 }}}

 An other solution is to create `tar.xz` files instead of `tar.gz`. This
 would also create smaller files.

--
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] #23136 [Applications/Tor Launcher]: moat integration (fetch bridges for the user)

[Tor Bug Tracker & Wiki]

#23136: moat integration (fetch bridges for the user)
---+
 Reporter:  mcs|  Owner:  brade
 Type:  defect | Status:  needs_revision
 Priority:  Very High  |  Milestone:
Component:  Applications/Tor Launcher  |Version:
 Severity:  Normal | Resolution:
 Keywords:  TorBrowserTeam201802   |  Actual Points:
Parent ID:  #24689 | Points:
 Reviewer: |Sponsor:  Sponsor4
---+
Changes (by mcs):

 * status:  needs_review => needs_revision
 * keywords:  TorBrowserTeam201802R => TorBrowserTeam201802


--
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] #25327 [Applications/Tor Browser]: debug files are not deterministic

[Tor Bug Tracker & Wiki]

#25327: debug files are not deterministic
+--
 Reporter:  boklm   |  Owner:  tbb-team
 Type:  defect  | Status:  needs_review
 Priority:  Medium  |  Milestone:
Component:  Applications/Tor Browser|Version:
 Severity:  Normal  | Resolution:
 Keywords:  TorBrowserTeam201802R, tbb-rbm  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by boklm):

 * keywords:  TorBrowserTeam201802, tbb-rbm => TorBrowserTeam201802R, tbb-
   rbm
 * status:  new => needs_review


Comment:

 In branch `bug_25327` I made a patch creating `*-debug.tar.xz` files
 instead of `*-debug.tar.gz` files:
 https://gitweb.torproject.org/user/boklm/tor-browser-
 build.git/commit/?h=bug_25327=3699792995ef75ff516fba20b1534e9722ab2f50

--
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] #23136 [Applications/Tor Launcher]: moat integration (fetch bridges for the user)

[Tor Bug Tracker & Wiki]

#23136: moat integration (fetch bridges for the user)
---+--
 Reporter:  mcs|  Owner:  brade
 Type:  defect | Status:  needs_review
 Priority:  Very High  |  Milestone:
Component:  Applications/Tor Launcher  |Version:
 Severity:  Normal | Resolution:
 Keywords:  TorBrowserTeam201802R  |  Actual Points:
Parent ID:  #24689 | Points:
 Reviewer: |Sponsor:  Sponsor4
---+--

Comment (by mcs):

 Replying to [comment:41 mcs]:
 > Agreed, and the potential for this kind of problem is what led us to use
 the TOR_PT_EXIT_ON_STDIN_CLOSE mechanism. In fact, Kathy and I thought
 this was working 100% of the time... but I was able to reproduce the
 problem you describe on Linux just now.

 It turns out that our code does not correctly handle the case where the
 user cancels during startup on meek-cient-torbrowser, e.g., during the PT
 negotiation. To fix it we will have to re-architect things a little. We
 expect to post a new patch later today.

--
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] #25249 [Core Tor/Tor]: Spec/implementation deviation in C protover code

[Tor Bug Tracker & Wiki]

#25249: Spec/implementation deviation in C protover code
--+
 Reporter:  nickm |  Owner:  nickm
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  033-must  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by nickm):

 * keywords:   => 033-must


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

Re: [tor-bugs] #25312 [Core Tor/Tor]: circ: We can pick an active circuit that is marked for close

[Tor Bug Tracker & Wiki]

#25312: circ: We can pick an active circuit that is marked for close
---+
 Reporter:  dgoulet|  Owner:  dgoulet
 Type:  defect | Status:  assigned
 Priority:  Medium |  Milestone:  Tor: 0.3.4.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  tor-cmux, tor-circuit  |  Actual Points:
Parent ID:  #25328 | Points:
 Reviewer: |Sponsor:
---+
Changes (by dgoulet):

 * parent:   => #25328


--
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] #25112 [Applications/Tor Browser]: Tor Browser 7.5 is not working on Windows Vista 64bit

[Tor Bug Tracker & Wiki]

#25112: Tor Browser 7.5 is not working on Windows Vista 64bit
-+-
 Reporter:  gk   |  Owner:
 |  pospeselr
 Type:  defect   | Status:
 |  needs_information
 Priority:  High |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Major| Resolution:
 Keywords:  ff60-esr-will-have,  |  Actual Points:
  TorBrowserTeam201802   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by cypherpunks):

 * status:  assigned => needs_information


Comment:

 Vista is vulnerable without security patches. Why are you wasting your
 resources on 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

[tor-bugs] #25329 [Metrics/Library]: Enable metrics-lib to process large (> 2G) logfiles

[Tor Bug Tracker & Wiki]

#25329: Enable metrics-lib to process large (> 2G) logfiles
-+--
 Reporter:  iwakeh   |  Owner:  metrics-team
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Metrics/Library  |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:  #25317
   Points:   |   Reviewer:
  Sponsor:   |
-+--
 Metrics-lib receives compressed logs, usually of sizes below 600kB.  As
 this can be dealt with in-memory, this ticket is about handling the logs
 that deflate to larger files (approx. 2G).

 Commons-compressed doesn't provide methods for determining the deflated
 content size (as the command line tool xz does).  Other compression types
 metrics-lib supports have this option, but it also would require more
 changes.

 Compression can be very effective. Thus, using a cut-off compressed size
 is sort of arbitrary.  An example for xz compression: the 3G deflated log
 has 589492 compressed input array length; using extreme compression it
 even shrinks to a length of 405480; on the other hand a deflated 64M file
 can have an input array of 509212 length.

 For handling larger log files with metrics-lib some interface changes will
 be necessary.  Here a suggestion:

 {{{

  public interface LogDescriptor extends Descriptor {

/**
 -   * Returns the decompressed raw descriptor bytes of the log.
 +   * Returns the compressed raw descriptor bytes of the log.
 +   *
 +   * For access to the log's decompressed bytes
 +   * use method {@code decompressedByteStream}.
 +   *
 * @since 2.2.0
 */

public byte[] getRawDescriptorBytes();

/**
 +   * Returns the decompressed raw descriptor bytes of the log as stream.
 +   *
 +   * @since 2.2.0
 +   */
 +  public InputStream decompressedByteStream();
 +

 }}}


 I think this might be easiest to understand and use; and of course the
 implementation wouldn't need to change processing for large and 'normal'
 logs.  It also avoids deciding about the method to find out if a file is
 large or not.

 Thoughts?

--
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] #25329 [Metrics/Library]: Enable metrics-lib to process large (> 2G) logfiles

[Tor Bug Tracker & Wiki]

#25329: Enable metrics-lib to process large (> 2G) logfiles
-+--
 Reporter:  iwakeh   |  Owner:  iwakeh
 Type:  enhancement  | Status:  accepted
 Priority:  Very High|  Milestone:
Component:  Metrics/Library  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:  #25317   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by iwakeh):

 * priority:  Medium => Very High
 * status:  new => accepted
 * owner:  metrics-team => iwakeh
 * cc: metrics-team (added)


Comment:

 Setting to very high as #25317 depends on this.

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

Re: [tor-bugs] #25317 [Metrics/CollecTor]: Enable webstats to process large (> 2G) logfiles

[Tor Bug Tracker & Wiki]

#25317: Enable webstats to process large (> 2G) logfiles
---+--
 Reporter:  iwakeh |  Owner:  iwakeh
 Type:  defect | Status:  assigned
 Priority:  High   |  Milestone:
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--

Comment (by iwakeh):

 See #25329 for the metrics-lib 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] #16472 [Applications/Tor Browser]: Upgrade Binutils to 2.25+ for Tor Browser builds

[Tor Bug Tracker & Wiki]

#16472: Upgrade Binutils to 2.25+ for Tor Browser builds
--+--
 Reporter:  gk|  Owner:  tbb-team
 Type:  task  | Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-rbm, boklm201802  |  Actual Points:
Parent ID:  #12968| Points:
 Reviewer:|Sponsor:
--+--

Comment (by ahomescu):

 I will investigate this on the selfrando end, should be able to fix it
 shortly.

--
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] #25317 [Metrics/CollecTor]: Enable webstats to process large (> 2G) logfiles

[Tor Bug Tracker & Wiki]

#25317: Enable webstats to process large (> 2G) logfiles
---+--
 Reporter:  iwakeh |  Owner:  iwakeh
 Type:  defect | Status:  accepted
 Priority:  High   |  Milestone:
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--
Changes (by iwakeh):

 * status:  assigned => accepted


--
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] #25275 [Internal Services/Service - git]: Please delete tag collector-1.5.0 in collector.git

[Tor Bug Tracker & Wiki]

#25275: Please delete tag collector-1.5.0 in collector.git
-+
 Reporter:  karsten  |  Owner:  tor-gitadm
 Type:  task | Status:  reopened
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service - git  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+
Changes (by karsten):

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


Comment:

 Hmm, are you sure this is fixed? I still see the 1.5.0 tag on
 https://gitweb.torproject.org/collector.git/, and when I clone the
 repository and run `git tag -l`, I see it, too.

 Do I have to push something to the repository first in order to make that
 tag go away? Or do I have to push a new 1.5.0 tag? Or...

--
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] #25327 [Applications/Tor Browser]: debug files are not deterministic

[Tor Bug Tracker & Wiki]

#25327: debug files are not deterministic
+--
 Reporter:  boklm   |  Owner:  tbb-team
 Type:  defect  | Status:  closed
 Priority:  Medium  |  Milestone:
Component:  Applications/Tor Browser|Version:
 Severity:  Normal  | Resolution:  fixed
 Keywords:  TorBrowserTeam201802R, tbb-rbm  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by gk):

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


Comment:

 Thanks, looks good to me. I merged that into `master` (commit
 3699792995ef75ff516fba20b1534e9722ab2f50).

--
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] #25112 [Applications/Tor Browser]: Tor Browser 7.5 is not working on Windows Vista 64bit

[Tor Bug Tracker & Wiki]

#25112: Tor Browser 7.5 is not working on Windows Vista 64bit
-+-
 Reporter:  gk   |  Owner:
 |  pospeselr
 Type:  defect   | Status:
 |  assigned
 Priority:  High |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Major| Resolution:
 Keywords:  ff60-esr-will-have,  |  Actual Points:
  TorBrowserTeam201802   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by cypherpunks):

 * status:  needs_information => assigned


Comment:

 Replying to [comment:9 cypherpunks]:
 > Vista is vulnerable without security patches. Why are you wasting your
 resources on it?
 But the current ESR of Firefox still supports Vista and XP, which means
 that TB should support them as well as ditch them when Firefox ditches
 them (i.e. this next ESR).

--
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] #25330 [Internal Services/Tor Sysadmin Team]: Create email & LDAP for Heather

[Tor Bug Tracker & Wiki]

#25330: Create email & LDAP for Heather
-+-
 Reporter:  ewyatt   |  Owner:  tpa
 Type:  task | Status:  new
 Priority:  High |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 {{{

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA512


 Please create email alias and LDAP account for Heather

 Hello,
 Please create email forwarding and LDAP account access for Heather, our
 new Chief Financial and Grants Officer. (Announcement coming soon after
 email address is set up.)
 Thank you!

 First name: Heather
 Last name: DeSellier
 Desired uid: heat...@torproject.org
 Forwarding address: hdesell...@riseup.net
 PGP: 47F0 EF06 FA65 38A8 F585  3132 8522 E35A FB63 DB63

 -BEGIN PGP SIGNATURE-
 Comment: GPGTools - https://gpgtools.org

 iQIzBAEBCgAdFiEENecqn2ZVRfkstmYkugyUAPgPkc4FAlqNu2UACgkQugyUAPgP
 kc7pcg//d4y35pk29ZMTIAXIxueTQVwokCOSMku1eeivDyM6nUdf/GQ2mD7FYyaF
 UDBiIAUrX+AS7+NJ845Ukj1wGS0YiUwot1KgTiIOJUg6A35LrQjwOr8S6L7BTZFX
 zTbLhawhNT/yeyBAAwMYx0FhzxZ7rJwwF00E8YmcxGKFszSaKHycZMG4wgClQh1K
 pQKEQlLVb/OBvmrgQvoTeMF87vt/bXtVpjmdjiZTTg+/spbyHgZ6hWRE1hrxUIxY
 jq/joZj8ABZUf+LsHsgP85I2tzaFh211xtybd//Y7CXjLbkcwUh6Pr0QBTw4jfsR
 219NJ9zSXQmBDhZ9sI+9Opfs7dV9eWFxWd/DoV+O/SjxV9noV8Kj1o0QphlvhufA
 dhqdK6ot6sftui/1cPT6KBTEVcrYASfdMQNPRuV/lW7Tsc8pAnw4hFS+uRik0u2Q
 LcFWUs/p73DnnNs2M6cxbgkCspXMxcHj557Ar/Nq7qmTyll/kaQ+vZNOKSAhm8uk
 xBqTGVcRpO96CtanPxwWzvCIgkmJviZ4lODL04X828sHz+B/826qV6xWncFnIl3U
 pY+hqtI/G2AWmw7+tTKZtcM7JysDtKMvwwzDBdxRky0eUQ6ZxOXEjsQPxd7io9UI
 lYlirYXPoHoitFkPOHU0i2+LfnQKm4AP+gpXYv+cbNRJB51RfpU=
 =MYPt
 -END PGP SIGNATURE-

 }}}

--
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] #25331 [Applications/Tor Browser]: Test from #18912 failing

[Tor Bug Tracker & Wiki]

#25331: Test from #18912 failing
--+--
 Reporter:  arthuredelstein   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 While preparing to uplift our [https://gitweb.torproject.org/tor-
 browser.git/patch/?id=36e1b88 patch] for #18912, I rebased it to mozilla-
 central but found one of the mochitests is failing. I then ran the test in
 the latest tor-browser.git branch (tor-browser-52.6.0esr-8.0-2) and saw
 the same test failure:

 {{{#!html
 
 0 INFO TEST-START | Shutdown
 1 INFO Passed:  30
 2 INFO Failed:  1
 3 INFO Todo:0
 4 INFO Mode:non-e10s
 5 INFO SimpleTest FINISHED
 The following tests failed:
 56 INFO TEST-UNEXPECTED-FAIL |
 toolkit/mozapps/update/tests/chrome/test_0790_check_certPinning_noUpdate.xul
 | Checking update.errorCode == MOZILLA_PKIX_ERROR_KEY_PINNING_FAILURE -
 got 2153390067, expected 2153398272
 SimpleTest.is@chrome://mochikit/content/tests/SimpleTest/SimpleTest.js:271:5
 
checkErrorCode@chrome://mochitests/content/chrome/toolkit/mozapps/update/tests/chrome/test_0790_check_certPinning_noUpdate.xul:61:3
 
defaultCallback@chrome://mochitests/content/chrome/toolkit/mozapps/update/tests/chrome/utils.js:429:5
 
 }}}
 Somehow we're not getting the desired error 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] #23136 [Applications/Tor Launcher]: moat integration (fetch bridges for the user)

[Tor Bug Tracker & Wiki]

#23136: moat integration (fetch bridges for the user)
---+--
 Reporter:  mcs|  Owner:  brade
 Type:  defect | Status:  needs_review
 Priority:  Very High  |  Milestone:
Component:  Applications/Tor Launcher  |Version:
 Severity:  Normal | Resolution:
 Keywords:  TorBrowserTeam201802R  |  Actual Points:
Parent ID:  #24689 | Points:
 Reviewer: |Sponsor:  Sponsor4
---+--
Changes (by mcs):

 * keywords:  TorBrowserTeam201802 => TorBrowserTeam201802R
 * status:  needs_revision => needs_review


Comment:

 Here is a fixup commit so you can see what we changed to fix the cancel
 problem:
 https://gitweb.torproject.org/user/brade/tor-
 launcher.git/commit/?h=bug23136-03=1e8cd277bc8380f9ce169c2ce990cf580323d917

 And here is the entire revised patch:
 https://gitweb.torproject.org/user/brade/tor-
 launcher.git/commit/?h=bug23136-04=d8ecbe221fbc691909cd4f070407901b531e6de8

--
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] #25306 [Core Tor/Tor]: tor_assertion_failed_(): Bug: ../src/or/hs_service.c:1985: rotate_all_descriptors: Assertion service->desc_current failed; aborting.

[Tor Bug Tracker & Wiki]

#25306: tor_assertion_failed_(): Bug: ../src/or/hs_service.c:1985:
rotate_all_descriptors: Assertion service->desc_current failed; aborting.
-+-
 Reporter:  cypherpunks  |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.3.2-alpha
 Severity:  Normal   | Resolution:
 Keywords:  tor-hs crash 033-must 032-backport   |  Actual Points:
  031-backport   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by teor):

 * keywords:  tor-hs crash 033-must 032-backport => tor-hs crash 033-must
 032-backport 031-backport


Comment:

 hs_service.c is also in maint-0.3.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] #22346 [Metrics/Statistics]: Investigate drop in Tor Browser update pings in early 2017 and 2018

[Tor Bug Tracker & Wiki]

#22346: Investigate drop in Tor Browser update pings in early 2017 and 2018
+--
 Reporter:  cypherpunks |  Owner:  metrics-team
 Type:  defect  | Status:  new
 Priority:  Medium  |  Milestone:
Component:  Metrics/Statistics  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--

Comment (by karsten):

 Replying to [comment:13 boklm]:
 > Yes, if you can send me a dump of this database, I will look more
 closely at the numbers from the drop around 2018-01-24 to try to
 understand it.

 Great! I just created a database dump and sent you the link via private
 mail.

--
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] #25329 [Metrics/Library]: Enable metrics-lib to process large (> 2G) logfiles

[Tor Bug Tracker & Wiki]

#25329: Enable metrics-lib to process large (> 2G) logfiles
-+---
 Reporter:  iwakeh   |  Owner:  iwakeh
 Type:  enhancement  | Status:  needs_information
 Priority:  Very High|  Milestone:
Component:  Metrics/Library  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:  #25317   | Points:
 Reviewer:   |Sponsor:
-+---

Comment (by karsten):

 And the reason to have `getRawDescriptorBytes()` return ''compressed'' raw
 descriptor bytes is that it has to return ''something'', as it's
 overridden from `Descriptor`?

 If so, works for me.

 If you make this change, please look out for surrounding comments that
 need changing. 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] #25324 [Core Tor/Tor]: Create a tor-releases.git repository.

[Tor Bug Tracker & Wiki]

#25324: Create a tor-releases.git repository.
--+
 Reporter:  nickm |  Owner:  (none)
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by teor):

 I like the idea of a separate repository.

 If we only lost supported releases, we may have to mark release branches
 as "ok to delete".

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