Re: [tor-bugs] #22564 [Applications/Tor Browser]: Hide firefox sync

[Tor Bug Tracker & Wiki]

#22564: Hide firefox sync
-+-
 Reporter:  Dbryrtfbcbhgf|  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-7.0-issues, tbb-regression,  |  Actual Points:
  TorBrowserTeam201802   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by cypherpunks):

 https://bugzilla.mozilla.org/show_bug.cgi?id=586985

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #19369 [Applications/Tor Browser]: On the privacy pane "Never Remember History" can't get selected

[Tor Bug Tracker & Wiki]

#19369: On the privacy pane "Never Remember History" can't get selected
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-6.0-issues, tbb-regression,  |  Actual Points:
  tbb-usability  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by cypherpunks):

 Since Firefox 44, by Mozilla's logic, "Never Remember History" means
 "Remember History" with PBM:
 {{{
  if (this._checkHistoryValues(this.prefsForKeepingHistory)) {
if (getVal("browser.privatebrowsing.autostart"))
  mode = "dontremember";
else
  mode = "remember";
  }
  else
mode = "custom";
 }}}
 See https://bugzilla.mozilla.org/show_bug.cgi?id=1203531

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25217 [Metrics]: metrics-base: Update checkstyle to debian stable

[Tor Bug Tracker & Wiki]

#25217: metrics-base: Update checkstyle to debian stable
-+--
 Reporter:  iwakeh   |  Owner:  metrics-team
 Type:  enhancement  | Status:  new
 Priority:  Low  |  Milestone:
Component:  Metrics  |Version:
 Severity:  Minor| Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by iwakeh):

 * priority:  Medium => Low
 * severity:  Normal => Minor


Comment:

 Setting to lesser prio and severity b/c we're waiting on Debian to upgrade
 to a version >= 6.17

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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:  metrics-team
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--

Comment (by iwakeh):

 Is it really necessary to do the slicing using java?  Assuming such
 imports are limited in number (once a year?) the slices could simply be
 provided by moving the logs to be imported in appropriate folder
 structures and run CollecTor for importing these.

 As this is still set to 'new', are you working on this while importing?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25022 [Metrics/Website]: Convert all scripts used for building to Ant tasks

[Tor Bug Tracker & Wiki]

#25022: Convert all scripts used for building to Ant tasks
-+--
 Reporter:  iwakeh   |  Owner:  iwakeh, metrics-team
 Type:  enhancement  | Status:  assigned
 Priority:  Medium   |  Milestone:
Component:  Metrics/Website  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by iwakeh):

 * owner:  iwakeh => iwakeh, metrics-team
 * status:  needs_revision => assigned


Comment:

 Replying to [comment:3 karsten]:
 > ...
 > The reason for leaving the generated JSPs under version control was that
 one wouldn't need to have to regenerate specs in order to build the
 website. Now we make that a requirement. I don't feel strongly about this.

 Ah, ok, the reasoning was that there are several tools needed, which might
 not generally be available,  and having the resulting pages in version
 control would help here.  So, the generated files should stay in git.
 I'll add a README file to the spec folder explaining this.

 >
 > (And again, I didn't get a notification for this ticket update...)

 Trying to assign the ticket to metrics-team, 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] #25022 [Metrics/Website]: Convert all scripts used for building to Ant tasks

[Tor Bug Tracker & Wiki]

#25022: Convert all scripts used for building to Ant tasks
-+--
 Reporter:  iwakeh   |  Owner:  iwakeh, metrics-team
 Type:  enhancement  | Status:  needs_information
 Priority:  Medium   |  Milestone:
Component:  Metrics/Website  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by iwakeh):

 * status:  assigned => 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

Re: [tor-bugs] #25022 [Metrics/Website]: Convert all scripts used for building to Ant tasks

[Tor Bug Tracker & Wiki]

#25022: Convert all scripts used for building to Ant tasks
-+--
 Reporter:  iwakeh   |  Owner:  iwakeh, metrics-team
 Type:  enhancement  | Status:  needs_information
 Priority:  Medium   |  Milestone:
Component:  Metrics/Website  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by iwakeh):

 * cc: metrics-team (removed)


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25229 [- Select a component]: Resist Spectre by using retpoline and a new instruction provided by Intel with microcode update

[Tor Bug Tracker & Wiki]

#25229: Resist Spectre by using retpoline and a new instruction provided by 
Intel
with microcode update
--+
 Reporter:  cypherpunks   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  High  |  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 you need to protect both browser and Tor.

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

Re: [tor-bugs] #17228 [Applications/Tor Browser]: Consideration for disabling referrers within TBB

[Tor Bug Tracker & Wiki]

#17228: Consideration for disabling referrers within TBB
--+--
 Reporter:  cypherpunks   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by cypherpunks):

 We just need a smarter fake referer generation algo taking in account such
 factors as type of content.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25230 [- Select a component]: Alternative way to report bad relays

[Tor Bug Tracker & Wiki]

#25230: Alternative way to report bad relays
--+
 Reporter:  cypherpunks   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 The user who leaved #25201 was advised to

 >Please let us know by sending email to bad-relays AT lists DOT torproject
 DOT org!


 It's not anonymous! Please start accepting reports via this bug tracker!

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25022 [Metrics/Website]: Convert all scripts used for building to Ant tasks

[Tor Bug Tracker & Wiki]

#25022: Convert all scripts used for building to Ant tasks
-+--
 Reporter:  iwakeh   |  Owner:  iwakeh, metrics-team
 Type:  enhancement  | Status:  needs_information
 Priority:  Medium   |  Milestone:
Component:  Metrics/Website  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by iwakeh):

 I think this is a mac issue.  Could you remove the first line from
 'convert.awk', i.e.
 {{{
 diff --git a/src/main/resources/spec/convert.awk
 b/src/main/resources/spec/convert.awk
 index ab26121..8535cba 100644
 --- a/src/main/resources/spec/convert.awk
 +++ b/src/main/resources/spec/convert.awk
 @@ -1,5 +1,3 @@
 -#!/usr/bin/awk -f
 -
  # Skip everything before  including generated header, script, and
 style.
  BEGIN {
insidebody = 0;
 }}}

 and try 'ant clean generate-specs' again?
 (I assume that 'awk' doesn't reside in '/usr/bin' on mac and that this
 causes the trouble.)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25201 [- Select a component]: Attention. Yet another exit node redirecting URL. Scan Tor now.

[Tor Bug Tracker & Wiki]

#25201: Attention. Yet another exit node redirecting URL. Scan Tor now.
--+--
 Reporter:  cypherpunks   |  Owner:  tbb-team
 Type:  defect| Status:  closed
 Priority:  High  |  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal| Resolution:  invalid
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by cypherpunks):

 * status:  new => closed
 * component:  Applications/Tor Browser => - Select a component
 * resolution:   => invalid


Comment:

 reporter got the required information (changed component sinc this is not
 tbb defect)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25230 [- Select a component]: Alternative way to report bad relays

[Tor Bug Tracker & Wiki]

#25230: Alternative way to report bad relays
--+
 Reporter:  cypherpunks   |  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):

 you can create an anonymous email account and submit your reports from
 that account

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25230 [- Select a component]: Alternative way to report bad relays

[Tor Bug Tracker & Wiki]

#25230: Alternative way to report bad relays
--+
 Reporter:  cypherpunks   |  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):

 You'll need Tor Mail for that.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25231 [Metrics/Website]: Restore metrics-lib submodule in metrics-web

[Tor Bug Tracker & Wiki]

#25231: Restore metrics-lib submodule in metrics-web
-+--
 Reporter:  iwakeh   |  Owner:  iwakeh, metrics-team
 Type:  defect   | Status:  assigned
 Priority:  Medium   |  Milestone:
Component:  Metrics/Website  |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+--
 The metrics-lib submodule got corrupted in [https://gitweb.torproject.org
 /metrics-
 web.git/commit/src/submods?id=73205cc3df76d0ca8d2fc62f26e2359093e73c7c
 this commit].  This is currently most problematic when checking out from
 scratch.

 I'll add a branch fixing this next.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25231 [Metrics/Website]: Restore metrics-lib submodule in metrics-web

[Tor Bug Tracker & Wiki]

#25231: Restore metrics-lib submodule in metrics-web
-+--
 Reporter:  iwakeh   |  Owner:  iwakeh, metrics-team
 Type:  defect   | Status:  needs_review
 Priority:  High |  Milestone:
Component:  Metrics/Website  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:  karsten  |Sponsor:
-+--
Changes (by iwakeh):

 * priority:  Medium => High
 * reviewer:   => karsten
 * status:  assigned => needs_review


Comment:

 Please review [https://gitweb.torproject.org/user/iwakeh/metrics-
 web.git/commit/?h=task-25231 this commit].

 Steps:
 {{{
 git clone  --branch task-25231 https://git.torproject.org/user/iwakeh
 /metrics-web.git mw-task-25131
 cd mw-task-25131/
 ./src/main/resources/bootstrap-development.sh
 }}}

 Both the metrics-lib submodule and the metrics-base submodule in metrics-
 lib should be checked out:
 {{{
 > ls src/submods/metrics-lib/
 build.xml  CERT  CHANGELOG.md  CONTRIB.md  LICENSE  README.md  src

 > ls src/submods/metrics-lib/src/build/java/
 base.xml  build.xml.template  junittest.policy  metrics_checks.xml
 stylesheet.css  tor-onion.png

 }}}

 After adding the 'lib' folder (as usual) ant task 'war' should complete
 successfully.

 Setting to high as #25022 depends on this and all other tickets for
 metrics-web.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25231 [Metrics/Website]: Restore metrics-lib submodule in metrics-web

[Tor Bug Tracker & Wiki]

#25231: Restore metrics-lib submodule in metrics-web
-+--
 Reporter:  iwakeh   |  Owner:  iwakeh, metrics-team
 Type:  defect   | Status:  needs_review
 Priority:  High |  Milestone:
Component:  Metrics/Website  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:  karsten  |Sponsor:
-+--
Changes (by iwakeh):

 * cc: metrics-team (added)


Comment:

 Adding metrics-team as cc, because the owner list doesn't seem to trigger
 bug-tracker mails.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25231 [Metrics/Website]: Restore metrics-lib submodule in metrics-web

[Tor Bug Tracker & Wiki]

#25231: Restore metrics-lib submodule in metrics-web
-+--
 Reporter:  iwakeh   |  Owner:  iwakeh
 Type:  defect   | Status:  assigned
 Priority:  High |  Milestone:
Component:  Metrics/Website  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:  karsten  |Sponsor:
-+--
Changes (by iwakeh):

 * status:  needs_review => assigned
 * owner:  iwakeh, metrics-team => iwakeh


Comment:

 Changing owner back.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25231 [Metrics/Website]: Restore metrics-lib submodule in metrics-web

[Tor Bug Tracker & Wiki]

#25231: Restore metrics-lib submodule in metrics-web
-+--
 Reporter:  iwakeh   |  Owner:  iwakeh
 Type:  defect   | Status:  needs_review
 Priority:  High |  Milestone:
Component:  Metrics/Website  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:  karsten  |Sponsor:
-+--
Changes (by iwakeh):

 * status:  assigned => needs_review


Comment:

 Restoring 'needs_review' setting.  (Sorry for all these mails! Just trying
 to find a way for missing update mails from track.  It seems we have to
 set cc to metrics-team always ...)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25232 [- Select a component]: DDG shortcut for normal and onion site is same

[Tor Bug Tracker & Wiki]

#25232: DDG shortcut for normal and onion site is same
--+
 Reporter:  kkm   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Low   |  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 Currently, the shortcut for search on DuckDuckGo and DuckDuckGo onion both
 point to #du.

 There should be a different shortcut for both.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25232 [- Select a component]: DDG shortcut for normal and onion site is same

[Tor Bug Tracker & Wiki]

#25232: DDG shortcut for normal and onion site is same
--+
 Reporter:  kkm   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Low   |  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by kkm):

 * Attachment "Screen Shot 2018-02-12 at 11.10.22.png" added.


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

Re: [tor-bugs] #25085 [Metrics/Onionoo]: Make order of sorted results deterministic

[Tor Bug Tracker & Wiki]

#25085: Make order of sorted results deterministic
-+--
 Reporter:  iwakeh   |  Owner:  iwakeh
 Type:  enhancement  | Status:  accepted
 Priority:  Medium   |  Milestone:
Component:  Metrics/Onionoo  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:  #25002   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by iwakeh):

 Please review
 [https://gitweb.torproject.org/user/iwakeh/onionoo.git/log/?h=task-25002
 two commits] on the rebased branch including the changelog entry.

 (Protocol update follows.)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25085 [Metrics/Onionoo]: Make order of sorted results deterministic

[Tor Bug Tracker & Wiki]

#25085: Make order of sorted results deterministic
-+--
 Reporter:  iwakeh   |  Owner:  iwakeh
 Type:  enhancement  | Status:  needs_review
 Priority:  Medium   |  Milestone:
Component:  Metrics/Onionoo  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:  #25002   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by iwakeh):

 * status:  accepted => needs_review


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

Re: [tor-bugs] #25230 [- Select a component]: Alternative way to report bad relays

[Tor Bug Tracker & Wiki]

#25230: Alternative way to report bad relays
--+
 Reporter:  cypherpunks   |  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):

 Replying to [comment:1 cypherpunks]:
 > you can create an anonymous email account and submit your reports from
 that account
 Know any email provider that doesn't kick Tor users or require to wait 2
 days or require SMS verification or or et cetera et cetera?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25230 [- Select a component]: Alternative way to report bad relays

[Tor Bug Tracker & Wiki]

#25230: Alternative way to report bad relays
--+
 Reporter:  cypherpunks   |  Owner:  (none)
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal| Resolution:  worksforme
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by cypherpunks):

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


Comment:

 https://trac.torproject.org/projects/tor/wiki/doc/EmailProvider

 please reopen if this is not satisfying to you

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

Re: [tor-bugs] #25085 [Metrics/Onionoo]: Make order of sorted results deterministic

[Tor Bug Tracker & Wiki]

#25085: Make order of sorted results deterministic
-+--
 Reporter:  iwakeh   |  Owner:  iwakeh
 Type:  enhancement  | Status:  needs_review
 Priority:  Medium   |  Milestone:
Component:  Metrics/Onionoo  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:  #25002   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by iwakeh):

 Please also review (and possibly improve)
 [https://gitweb.torproject.org/user/iwakeh/metrics-
 web.git/commit/?h=task-25085 the specification 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] #25198 [Community/Tor Browser Manual]: User manual should explain Tor Browser features more

[Tor Bug Tracker & Wiki]

#25198: User manual should explain Tor Browser features more
--+---
 Reporter:  arthuredelstein   |  Owner:  phoul
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Community/Tor Browser Manual  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---
Changes (by antonela):

 * cc: antonela (added)


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

[tor-bugs] #25233 [Internal Services/Tor Sysadmin Team]: weschniakowii shows old certificate for ooni.tpo in ~1/6 cases

[Tor Bug Tracker & Wiki]

#25233: weschniakowii shows old certificate for ooni.tpo in ~1/6 cases
-+-
 Reporter:  darkk|  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:   |
-+-
 Our prometheus instance alerted that ooni.tpo certificate expires in less
 than 25 days. Seems, one of httpd workers at weschniakowii
 (2001:6b0:5a:5000::5, 89.45.235.21) is stuck with old certificate.

 [https://atlas.ripe.net/measurements/11287106/#!probes Majority of probes]
 see new certificate with `Not Before 2018-02-02T00:37:31Z`, but ~1/6 of
 probes see old one with `Not Before 2017-12-04T00:40:56Z` that expires in
 couple of weeks.


 The issue is observable both with IPv4 and IPv6.

 Please, restart the worker before cert expires :-) Also, it may be
 interesting to understand the reason for worker to spend week and a half
 in "graceful restart" mode. Maybe that's some bug or something like
 slowloris attack going on.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25234 [Applications/Tor Browser]: Some NoScript whitelists may become permanent

[Tor Bug Tracker & Wiki]

#25234: Some NoScript whitelists may become permanent
--+--
 Reporter:  cypherpunks   |  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:|
--+--
 I have several Tor Browser profiles and I just noticed that on two of them
 there are some permanently whitelisted addresses.

 https://localhost.megasyncloopback.mega.nz:6342
 https://rogueleague.org:57333
 https://webirc.oftc.net:8443

 One profile had all of these while the other one had just mega.nz's.
 Seeing it one two separate profiles suggests it wasn't an isolated case.
 Each profile is a few months old and have been through several Tor Browser
 updates. Currently on 8.0a1 (win64)

 I'm not sure how to reproduce these. Though I believe it happened after
 temporarily enabling javascript on these websites. The first one probably
 requires downloading a file through mega.nz.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24769 [Core Tor/Tor]: Increase client idle and connection timeouts to reduce network load

[Tor Bug Tracker & Wiki]

#24769: Increase client idle and connection timeouts to reduce network load
-+-
 Reporter:  teor |  Owner:
 |  mikeperry
 Type:  defect   | Status:
 |  needs_review
 Priority:  High |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.1.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  tor-client, dos-resistance,  |  Actual Points:
  032-backport, 031-backport, 029-backport, 025  |
  -backport-maybe, review-group-32, 033-must |
Parent ID:   | Points:  1
 Reviewer:  nickm|Sponsor:
-+-
Changes (by nickm):

 * reviewer:   => 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] #25188 [Core Tor/Tor]: Spec bug in formal definition of Document in dir-spec.txt

[Tor Bug Tracker & Wiki]

#25188: Spec bug in formal definition of Document in dir-spec.txt
---+---
 Reporter:  witchof0x20|  Owner:  (none)
 Type:  enhancement| Status:  needs_review
 Priority:  Very Low   |  Milestone:  Tor:
   |  0.3.4.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Trivial| Resolution:
 Keywords:  tor-spec, review-group-32  |  Actual Points:
Parent ID: | Points:  0.1
 Reviewer:  nickm  |Sponsor:
---+---
Changes (by nickm):

 * reviewer:   => 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] #24767 [Core Tor/Tor]: All relays are constantly connecting to down relays and failing over and over

[Tor Bug Tracker & Wiki]

#24767: All relays are constantly connecting to down relays and failing over and
over
-+-
 Reporter:  arma |  Owner:  dgoulet
 Type:  enhancement  | Status:
 |  needs_review
 Priority:  Very High|  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-relay, tor-dos, performance, |  Actual Points:
  review-group-32, 033-must  |
Parent ID:   | Points:
 Reviewer:  asn  |Sponsor:
-+-

Comment (by dgoulet):

 OnionGit: https://oniongit.eu/dgoulet/tor/merge_requests/21

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25234 [Applications/Tor Browser]: Some NoScript whitelists may become permanent

[Tor Bug Tracker & Wiki]

#25234: Some NoScript whitelists may become permanent
--+--
 Reporter:  cypherpunks   |  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):

 * Attachment "noscript.png" added.

 Screenshot

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24902 [Core Tor/Tor]: Denial of Service mitigation subsystem

[Tor Bug Tracker & Wiki]

#24902: Denial of Service mitigation subsystem
-+-
 Reporter:  dgoulet  |  Owner:  dgoulet
 Type:  enhancement  | Status:
 |  needs_revision
 Priority:  Very High|  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ddos, tor-relay, review-group-30,|  Actual Points:
  029-backport, 031-backport, 032-backport,  |
  review-group-31, SponsorV  |
Parent ID:   | Points:
 Reviewer:  arma |Sponsor:
-+-

Comment (by dgoulet):

 Replying to [comment:69 teor]:
 > My relay radia4 became unmeasured shortly after I disabled my firewall
 and started relying on the DDoS defences. And then a few hours later, it
 was measured again.
 >
 > I've checked that it's reachable on IPv4 and IPv6, and that the
 remaining firewall rules aren't blocking anything (unless the authorities
 are making *lots* of connections).
 >
 > Could the authorities (or the bandwidth authority clients) be triggering
 one of the defences?
 > Aren't authorities meant to be exempted as relays?

 For reachability test, authority opens a one-hop circuit to the relay and
 it is authenticated right? But anycase, there is no defense applied for
 known IPs and I assume dirauth are very known.

 > Perhaps the bandwidth authority clients are building too many circuits?

 If the bwauth is opening more than 3 concurrent connections and doing on
 them 90 circuits burst at a rate of 3 circuit/second, then yes that is
 *crazy* and would trigger the defense. Or if it is opening more than 100
 TCP connections in parallel, all the other connections would get refused.

 > Edit: it was re-measured, not down

 The defense would be up for 60 minutes + rand(1, 30) minutes so if it was
 re-measured somehow properly without triggering the defense, I think that
 either the bwauth is on the edge there or it is not that.

 If the bwauth aren't opening that many circuits, I would blame the network
 load or/and bwauth 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] #24902 [Core Tor/Tor]: Denial of Service mitigation subsystem

[Tor Bug Tracker & Wiki]

#24902: Denial of Service mitigation subsystem
-+-
 Reporter:  dgoulet  |  Owner:  dgoulet
 Type:  enhancement  | Status:
 |  needs_revision
 Priority:  Very High|  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ddos, tor-relay, review-group-30,|  Actual Points:
  029-backport, 031-backport, 032-backport,  |
  review-group-31, SponsorV  |
Parent ID:   | Points:
 Reviewer:  arma |Sponsor:
-+-

Comment (by dgoulet):

 For the man page comment, I propose we start opening ticket to fix those
 because the `ticket24902_029_05` branch is becoming a monster that must be
 insync with 033. So I think I would avoid anything new in that branch
 until we backport it and then we apply the fixes on upstream 029 ?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25170 [Core Tor/Tor]: explicitly mention email address to contact for rejected relays

[Tor Bug Tracker & Wiki]

#25170: explicitly mention email address to contact for rejected relays
+
 Reporter:  cypherpunks |  Owner:  dgoulet
 Type:  enhancement | Status:  reopened
 Priority:  Low |  Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Minor   | Resolution:
 Keywords:  032-backport-maybe  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+
Changes (by nickm):

 * milestone:  Tor: 0.3.3.x-final => Tor: 0.3.2.x-final


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

Re: [tor-bugs] #25170 [Core Tor/Tor]: explicitly mention email address to contact for rejected relays

[Tor Bug Tracker & Wiki]

#25170: explicitly mention email address to contact for rejected relays
+
 Reporter:  cypherpunks |  Owner:  dgoulet
 Type:  enhancement | Status:  closed
 Priority:  Low |  Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Minor   | Resolution:  implemented
 Keywords:  032-backport-maybe  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+
Changes (by nickm):

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


Comment:

 It looks like a  harmless backport, since it only affects strings. Cherry-
 picked to maint-0.2.9 and merged forward.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25183 [Core Tor/Tor]: Implement a way to tell if an IP address is a known relay

[Tor Bug Tracker & Wiki]

#25183: Implement a way to tell if an IP address is a known relay
-+-
 Reporter:  dgoulet  |  Owner:  dgoulet
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  tor-relay, tor-dos, 029-backport,|  Actual Points:
  031-backport, 032-backport |
Parent ID:  #24902   | Points:
 Reviewer:  dgoulet  |Sponsor:
-+-

Comment (by nickm):

 To give my rationale for making the AF_UNSPEC change: I think it's
 harmless to have AF_UNSPEC be a constant in the current usage, but it's
 fragile.  When we promise a keyed hash, we ought to implement one, or we
 might find ourselves surprised later on.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25188 [Core Tor/Tor]: Spec bug in formal definition of Document in dir-spec.txt

[Tor Bug Tracker & Wiki]

#25188: Spec bug in formal definition of Document in dir-spec.txt
---+---
 Reporter:  witchof0x20|  Owner:  (none)
 Type:  enhancement| Status:  needs_revision
 Priority:  Very Low   |  Milestone:  Tor:
   |  0.3.4.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Trivial| Resolution:
 Keywords:  tor-spec, review-group-32  |  Actual Points:
Parent ID: | Points:  0.1
 Reviewer:  nickm  |Sponsor:
---+---
Changes (by nickm):

 * status:  needs_review => needs_revision


Comment:

 I think, given the amount of existing code out there,  we'd be better off
 changing the spec to match the implementation.  Is that something you'd be
 able to write a patch for, or would you like somebody else to take this
 over?

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

[tor-bugs] #25235 [Core Tor]: Guard node is not pinned

[Tor Bug Tracker & Wiki]

#25235: Guard node is not pinned
-+
 Reporter:  cypherpunks  |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Core Tor |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+
 I see guard node changing every circuit. Is it intended?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25235 [Core Tor]: Guard node is not pinned

[Tor Bug Tracker & Wiki]

#25235: Guard node is not pinned
-+
 Reporter:  cypherpunks  |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Core Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+

Comment (by cypherpunks):

 Can you see how many guard fingerprints are mentioned in your state file?
 Also what is your setup (i.e. Tor Browser? or something else??)?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25235 [Core Tor]: Guard node is not pinned

[Tor Bug Tracker & Wiki]

#25235: Guard node is not pinned
-+---
 Reporter:  cypherpunks  |  Owner:  (none)
 Type:  defect   | Status:  needs_information
 Priority:  Medium   |  Milestone:
Component:  Core Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+---
Changes (by cypherpunks):

 * status:  new => 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

Re: [tor-bugs] #25171 [Core Tor/Tor]: Clarify 'recognized' field in tor-spec

[Tor Bug Tracker & Wiki]

#25171: Clarify 'recognized' field in tor-spec
+--
 Reporter:  atagar  |  Owner:  (none)
 Type:  defect  | Status:  closed
 Priority:  Very Low|  Milestone:  Tor:
|  0.3.3.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Trivial | Resolution:  fixed
 Keywords:  tor-spec, doc, review-group-32  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  nickm   |Sponsor:
+--
Changes (by nickm):

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


Comment:

 Thanks, atagar!  I think this is as improvement over the existing spec.

 I've merged it, and made a couple of small tweaks in ef91cd6a595128.  The
 main one is that I don't think MAY is right here either: as I read RFC
 2119, "MAY "is for things that implementations are allowed to do, not for
 circumstances that will periodically occur.

 I've gone with this tweak on your wording:
 {{{
 +   When receiving and decrypting cells the 'recognized' will always be
 +   zero if we're the endpoint that the cell is destined for.  For cells
 +   that we should relay, the 'recognized' field will usually be nonzero,
 +   but will accidentally be zero with P=2^-32.
 }}}

 Thanks again for the spec fix!

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25235 [Core Tor/Tor]: Guard node is not pinned

[Tor Bug Tracker & Wiki]

#25235: Guard node is not pinned
--+---
 Reporter:  cypherpunks   |  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 nickm):

 * component:  Core Tor => Core Tor/Tor


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

Re: [tor-bugs] #25232 [- Select a component]: DDG shortcut for normal and onion site is same

[Tor Bug Tracker & Wiki]

#25232: DDG shortcut for normal and onion site is same
--+-
 Reporter:  kkm   |  Owner:  (none)
 Type:  defect| Status:  closed
 Priority:  Low   |  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal| Resolution:  invalid
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+-
Changes (by kkm):

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


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #23046 [Metrics/Library]: Add sub-interface LogDescriptor.LogLine (and the extension to WebServerAccessLogLine)

[Tor Bug Tracker & Wiki]

#23046: Add sub-interface LogDescriptor.LogLine (and the extension to
WebServerAccessLogLine)
-+---
 Reporter:  iwakeh   |  Owner:  iwakeh
 Type:  enhancement  | Status:  needs_review
 Priority:  Medium   |  Milestone:  metrics-lib 2.2.0
Component:  Metrics/Library  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  metrics-2018 |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+---
Changes (by iwakeh):

 * cc: metrics-team (added)
 * status:  accepted => needs_review


Comment:

 Please review [https://gitweb.torproject.org/user/iwakeh/metrics-
 lib.git/commit/?h=task-23046 this branch] based on the current master
 implementation.

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

Re: [tor-bugs] #25202 [Core Tor/Tor]: Check the calculations in cc_stats_refill_bucket using non fatal assertions

[Tor Bug Tracker & Wiki]

#25202: Check the calculations in cc_stats_refill_bucket using non fatal 
assertions
--+
 Reporter:  teor  |  Owner:  dgoulet
 Type:  defect| Status:  accepted
 Priority:  Low   |  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tor-dos, review-group-32  |  Actual Points:
Parent ID:| Points:  0.1
 Reviewer:|Sponsor:
--+
Changes (by dgoulet):

 * owner:  (none) => dgoulet
 * reviewer:  dgoulet =>
 * status:  needs_review => accepted
 * parent:  #24902 =>


Comment:

 Oh hey, I still like this change but I would like to hold off on it until
 we get #24902 backported else we keep piling up things on
 `ticket24902_029_05` which is getting big!

 So I'll put this back in `Assigned`, unparent it and and flag it for
 backport. I'll make a branch based on 029 once the above is merged.

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

Re: [tor-bugs] #25202 [Core Tor/Tor]: Check the calculations in cc_stats_refill_bucket using non fatal assertions

[Tor Bug Tracker & Wiki]

#25202: Check the calculations in cc_stats_refill_bucket using non fatal 
assertions
-+-
 Reporter:  teor |  Owner:  dgoulet
 Type:  defect   | Status:
 |  accepted
 Priority:  Low  |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-dos, review-group-32,|  Actual Points:
  029-backport, 031-backport, 032-backport   |
Parent ID:   | Points:  0.1
 Reviewer:   |Sponsor:
-+-
Changes (by dgoulet):

 * keywords:  tor-dos, review-group-32 => tor-dos, review-group-32,
 029-backport, 031-backport, 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] #25202 [Core Tor/Tor]: Check the calculations in cc_stats_refill_bucket using non fatal assertions

[Tor Bug Tracker & Wiki]

#25202: Check the calculations in cc_stats_refill_bucket using non fatal 
assertions
-+-
 Reporter:  teor |  Owner:  dgoulet
 Type:  defect   | Status:
 |  accepted
 Priority:  Low  |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-dos, review-group-32,|  Actual Points:
  029-backport, 031-backport, 032-backport,  |
  033-must   |
Parent ID:   | Points:  0.1
 Reviewer:   |Sponsor:
-+-
Changes (by dgoulet):

 * keywords:  tor-dos, review-group-32, 029-backport, 031-backport,
 032-backport =>
 tor-dos, review-group-32, 029-backport, 031-backport, 032-backport,
 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] #25095 [Core Tor/Tor]: Update dir-spec.txt with recent consensus param additions

[Tor Bug Tracker & Wiki]

#25095: Update dir-spec.txt with recent consensus param additions
---+
 Reporter:  arma   |  Owner:  dgoulet
 Type:  task   | Status:  needs_review
 Priority:  Medium |  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  tor-spec, tor-dos  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+
Changes (by dgoulet):

 * status:  accepted => needs_review


Comment:

 Spec branch: `ticket25095_01`

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25202 [Core Tor/Tor]: Check the calculations in cc_stats_refill_bucket using non fatal assertions

[Tor Bug Tracker & Wiki]

#25202: Check the calculations in cc_stats_refill_bucket using non fatal 
assertions
+--
 Reporter:  teor|  Owner:  dgoulet
 Type:  defect  | Status:  accepted
 Priority:  Low |  Milestone:  Tor:
|  0.3.3.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  tor-dos, review-group-32, 033-must  |  Actual Points:
Parent ID:  #24902  | Points:  0.1
 Reviewer:  |Sponsor:
+--
Changes (by dgoulet):

 * keywords:
 tor-dos, review-group-32, 029-backport, 031-backport, 032-backport,
 033-must
 => tor-dos, review-group-32, 033-must
 * parent:   => #24902


Comment:

 Scratch the above as a discussion with nickm, we'll pile on 24902 so we
 can put it in 033 before any 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] #22423 [Metrics/Website]: Refactor R code to use modern R packages and methods

[Tor Bug Tracker & Wiki]

#22423: Refactor R code to use modern R packages and methods
+--
 Reporter:  johnbwilliams   |  Owner:  metrics-team
 Type:  enhancement | Status:  assigned
 Priority:  Medium  |  Milestone:
Component:  Metrics/Website |Version:
 Severity:  Minor   | Resolution:
 Keywords:  plot_networksize()  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by karsten):

 * owner:  karsten => metrics-team
 * status:  accepted => assigned


Comment:

 I made more changes, but I need to pause for a while and do other stuff
 now. In the meantime I'm giving this ticket back to the metrics-team pool.

 If somebody feels like reviewing some R code, please take a look at the
 three functions at the end of `graphs.R`, namely `plot_relays_ipv6`,
 `plot_bridges_ipv6`, and `plot_advbw_ipv6`: https://gitweb.torproject.org
 /metrics-web.git/tree/src/main/R/rserver/graphs.R#n1097 ; these would then
 serve as blueprints for the other graphs.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25223 [Core Tor/Tor]: dos: dos_new_client_conn: Non-fatal assertion !(entry == NULL) failed

[Tor Bug Tracker & Wiki]

#25223: dos: dos_new_client_conn: Non-fatal assertion !(entry == NULL) failed
--+
 Reporter:  dgoulet   |  Owner:  dgoulet
 Type:  defect| Status:  needs_review
 Priority:  High  |  Milestone:  Tor:
  |  0.3.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tor-dos, tor-relay, 033-must  |  Actual Points:
Parent ID:  #24902| Points:
 Reviewer:|Sponsor:
--+
Changes (by dgoulet):

 * status:  assigned => needs_review
 * parent:   => #24902


Comment:

 Branch: `bug25223_029_01`

 Based on ticket24902_029_05 branch. Once ACK, I'll merge this into that
 parent branch for the 029 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] #25202 [Core Tor/Tor]: Check the calculations in cc_stats_refill_bucket using non fatal assertions

[Tor Bug Tracker & Wiki]

#25202: Check the calculations in cc_stats_refill_bucket using non fatal 
assertions
+--
 Reporter:  teor|  Owner:  dgoulet
 Type:  defect  | Status:
|  needs_review
 Priority:  Low |  Milestone:  Tor:
|  0.3.3.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  tor-dos, review-group-32, 033-must  |  Actual Points:
Parent ID:  #24902  | Points:  0.1
 Reviewer:  |Sponsor:
+--
Changes (by dgoulet):

 * status:  accepted => needs_review


Comment:

 See branch `ticket25202_029_01`.

 Based on ticket24902_029_05 branch. Once ACK, I'll merge this into that
 parent branch for the 029 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] #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:  metrics-team
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--

Comment (by karsten):

 Replying to [comment:4 iwakeh]:
 > Is it really necessary to do the slicing using java?  Assuming such
 imports are limited in number (once a year?) the slices could simply be
 provided by moving the logs to be imported in appropriate folder
 structures and run CollecTor for importing these.

 You mean we should prepare slices manually? How many slices would we need?
 Just one per year?

 > As this is still set to 'new', are you working on this while importing?

 I'm not working on this. I'm waiting for new hardware to arrive that has
 more than 16G RAM. I hope to have that available by next week. Feel free
 to grab the ticket in the meantime!

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25236 [Core Tor/Tor]: dos: Document torrc default values in the man page when not in the consensus

[Tor Bug Tracker & Wiki]

#25236: dos: Document torrc default values in the man page when not in the
consensus
--+---
 Reporter:  dgoulet   |  Owner:  dgoulet
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal|   Keywords:  tor-dos, manpage, tor-doc
Actual Points:|  Parent ID:  #24902
   Points:|   Reviewer:
  Sponsor:|
--+---
 From:

 https://trac.torproject.org/projects/tor/ticket/24902#comment:68

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24902 [Core Tor/Tor]: Denial of Service mitigation subsystem

[Tor Bug Tracker & Wiki]

#24902: Denial of Service mitigation subsystem
-+-
 Reporter:  dgoulet  |  Owner:  dgoulet
 Type:  enhancement  | Status:
 |  merge_ready
 Priority:  Very High|  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-dos, tor-relay, review-  |  Actual Points:
  group-30, 029-backport, 031-backport,  |
  032-backport, review-group-31, SponsorV|
Parent ID:   | Points:
 Reviewer:  arma |Sponsor:
-+-
Changes (by dgoulet):

 * status:  needs_revision => merge_ready
 * keywords:
 ddos, tor-relay, review-group-30, 029-backport, 031-backport,
 032-backport, review-group-31, SponsorV
 =>
 tor-dos, tor-relay, review-group-30, 029-backport, 031-backport,
 032-backport, review-group-31, SponsorV


Comment:

 For the man page fixes: #25236

 Setting this back in `merge_ready` for the 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] #25236 [Core Tor/Tor]: dos: Document torrc default values in the man page when not in the consensus

[Tor Bug Tracker & Wiki]

#25236: dos: Document torrc default values in the man page when not in the
consensus
---+---
 Reporter:  dgoulet|  Owner:  dgoulet
 Type:  defect | Status:  needs_review
 Priority:  Medium |  Milestone:  Tor:
   |  0.3.3.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  tor-dos, manpage, tor-doc  |  Actual Points:
Parent ID:  #24902 | Points:
 Reviewer: |Sponsor:
---+---
Changes (by dgoulet):

 * status:  assigned => needs_review


Comment:

 Branch: `bug25236_029_01`

 Based on ticket24902_029_05 branch. Once ACK, I'll merge this into that
 parent branch for the 029 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] #24815 [Core Tor/Tor]: Validate shared random state dates before each voting period

[Tor Bug Tracker & Wiki]

#24815: Validate shared random state dates before each voting period
--+
 Reporter:  teor  |  Owner:  dgoulet
 Type:  defect| Status:  needs_information
 Priority:  Medium|  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor  |Version:  Tor: 0.2.9.1-alpha
 Severity:  Normal| Resolution:
 Keywords:  tor-sr, tor-ddos  |  Actual Points:
Parent ID:| Points:  1
 Reviewer:|Sponsor:
--+
Changes (by dgoulet):

 * cc: teor (added)
 * status:  assigned => needs_information


Comment:

 From the log you sent me, I noticed that the voting period are
 synchronized. Is it possible we are in a timezone issue situation here
 because if I take your local timezone and convert it to UTC, the logs do
 add up:

 {{{
 Jan 07 09:48:14.984 [info] sr_state_update: SR: State prepared for
 upcoming voting period (2018-01-06 23:00:00). Upcoming phase is reveal
 (counters: 0 commit & 1 reveal rounds).
 }}}

 09:48 Australia Time -> 22:48 UTC so the upcoming voting period is indeed
 23:00 UTC.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #19926 [Core Tor/Tor]: BUG warning in connection_ap_attach_pending: waiting for rendezvous desc :*

[Tor Bug Tracker & Wiki]

#19926: BUG warning in connection_ap_attach_pending: waiting for rendezvous 
desc :*
-+-
 Reporter:  cypherpunks  |  Owner:  dgoulet
 Type:  defect   | Status:
 |  accepted
 Priority:  Low  |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.9.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  bug, regression, tor-hs, |  Actual Points:
  refactoring, easy  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by dgoulet):

 * keywords:  bug, regression, tor-hs => bug, regression, tor-hs,
 refactoring, easy
 * priority:  Medium => Low
 * milestone:  Tor: 0.3.3.x-final => Tor: unspecified


Comment:

 I'm a bit doubtful that iptables can break the SOCKS requests here unless
 it is applied on localhost and the SocksPort... would be a bit surprising?

 To hunt down this, it is mostly refactoring at this point to try to hunt
 it down.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25226 [Core Tor/Tor]: Circuit cell queue can fill up memory

[Tor Bug Tracker & Wiki]

#25226: Circuit cell queue can fill up memory
--+
 Reporter:  dgoulet   |  Owner:  dgoulet
 Type:  defect| Status:  accepted
 Priority:  Medium|  Milestone:  Tor:
  |  0.3.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tor-cell, tor-relay, tor-dos  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by dgoulet):

 * status:  needs_information => accepted
 * owner:  (none) => dgoulet


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24229 [Metrics/Website]: Provide BGP Data Collection on Tor Metrics

[Tor Bug Tracker & Wiki]

#24229: Provide BGP Data Collection on Tor Metrics
-+---
 Reporter:  iwakeh   |  Owner:  iwakeh
 Type:  enhancement  | Status:  needs_information
 Priority:  Medium   |  Milestone:
Component:  Metrics/Website  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+---
Changes (by iwakeh):

 * status:  accepted => needs_information


Comment:

 Suggested file structure for external data provided by CollecTor:
 `https://collector.torproject.org/third-party-archive/`

 The next level will consist of the third party main name, i.e., the path
 for BGP Data:
 `https://collector.torproject.org/third-party-archive/`

 Below the thrid party main level there could be `archive`, `source-code`,
 and `docs`.  For example: `https://collector.torproject.org/third-party-
 archive//archive` will contain the files `-mm-
 updates.txt.xz`, `https://collector.torproject.org/third-party-
 archive//source-code` just the `detection.py` script,
 and the provided documentation `counter-raptor.html` will be in
 `https://collector.torproject.org/third-party-archive//doc` slightly adapted to point to prevent broken links, if
 possible.

 The official documentation will be a jsp file based on the provided
 documentation. The path for the documentation integrated to metrics.tp.o
 could be `https://metrics.torproject.org/counter-raptor.html`, which will
 be linked from [https://metrics.torproject.org/sources.html#other Other
 sources].

 If the above paths are agreed on:
 * the jsp and referring links need to be created and
 * files need to be copied to the new structure below
 `https://collector.torproject.org/third-party-archive/`.

 Thoughts, additions, suggestions?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25061 [Core Tor/Tor]: Relays consider it a bootstrapping failure if they can't extend for somebody else's circuit

[Tor Bug Tracker & Wiki]

#25061: Relays consider it a bootstrapping failure if they can't extend for
somebody else's circuit
+
 Reporter:  arma|  Owner:  (none)
 Type:  defect  | Status:  new
 Priority:  Medium  |  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  backport-032, 033-must  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+
Changes (by dgoulet):

 * keywords:  backport-032 => backport-032, 033-must


Comment:

 I'm "must-ing" this ticket because I think we should avoid printing those
 and should properly report the bootstrap failure.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24229 [Metrics/Website]: Provide BGP Data Collection on Tor Metrics

[Tor Bug Tracker & Wiki]

#24229: Provide BGP Data Collection on Tor Metrics
-+---
 Reporter:  iwakeh   |  Owner:  iwakeh
 Type:  enhancement  | Status:  needs_information
 Priority:  Medium   |  Milestone:
Component:  Metrics/Website  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+---
Changes (by iwakeh):

 * cc: metrics-team (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] #24229 [Metrics/Website]: Provide BGP Data Collection on Tor Metrics

[Tor Bug Tracker & Wiki]

#24229: Provide BGP Data Collection on Tor Metrics
-+---
 Reporter:  iwakeh   |  Owner:  iwakeh
 Type:  enhancement  | Status:  needs_information
 Priority:  Medium   |  Milestone:
Component:  Metrics/Website  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+---

Comment (by iwakeh):

 Addition to comment:2: The data update process needs to be defined still.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #17945 [Core Tor/Tor]: Stop Tor2Web connecting to (Rendezvous) Single Onion Services

[Tor Bug Tracker & Wiki]

#17945: Stop Tor2Web connecting to (Rendezvous) Single Onion Services
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor2web, tor-hs, 029-proposed, 029   |  Actual Points:
  -teor-no, needs-design, needs-proposal-maybe,  |
  single-onion   |
Parent ID:  #24962   | Points:  5
 Reviewer:   |Sponsor:
-+-

Comment (by dgoulet):

 So I think in theory this should be simple. Once we splice the rend
 circuit, we should asses that the `p_chan` *and* the `n_chan` are both
 client (`channel_is_client()`). If so, we close both sides with a remote
 reason.

 Either we go with `END_CIRC_REASON_TORPROTOCOL` but then we have to bake
 it in the tor spec I think that we don't allow both ways to be single hop.
 Or something like `END_CIRC_REASON_DESTROYED`... I think we just need a
 reason that will make the tor2web client not retry again and again the
 same RP.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25237 [Core Tor/Tor]: spec: Document our circuit close reasons

[Tor Bug Tracker & Wiki]

#25237: spec: Document our circuit close reasons
--+
 Reporter:  dgoulet   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.3.4.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal|   Keywords:  tor-spec
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 In `or.h`, we define the reason to close a circuit:

 {{{
 /* Reasons why we (or a remote OR) might close a circuit. See tor-spec.txt
 for
  * documentation of these. */
 #define END_CIRC_REASON_MIN_0
 #define END_CIRC_REASON_NONE0
 #define END_CIRC_REASON_TORPROTOCOL 1
 #define END_CIRC_REASON_INTERNAL2
 #define END_CIRC_REASON_REQUESTED   3
 ...
 }}}

 Even though it says "See tor-spec.txt", those values aren't defined at all
 in tor-spec.txt, only the stream reasons are.

 This is a bit annoying because these values don't have any documentation
 on why and when they should be used.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #22423 [Metrics/Website]: Refactor R code to use modern R packages and methods

[Tor Bug Tracker & Wiki]

#22423: Refactor R code to use modern R packages and methods
+--
 Reporter:  johnbwilliams   |  Owner:  iwakeh
 Type:  enhancement | Status:  assigned
 Priority:  Medium  |  Milestone:
Component:  Metrics/Website |Version:
 Severity:  Minor   | Resolution:
 Keywords:  plot_networksize()  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by iwakeh):

 * owner:  metrics-team => iwakeh


Comment:

 Grabbing the review to also push #24707 a little.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #17945 [Core Tor/Tor]: Stop Tor2Web connecting to (Rendezvous) Single Onion Services

[Tor Bug Tracker & Wiki]

#17945: Stop Tor2Web connecting to (Rendezvous) Single Onion Services
-+-
 Reporter:  teor |  Owner:  dgoulet
 Type:  enhancement  | Status:
 |  accepted
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor2web, tor-hs, 029-proposed, 029   |  Actual Points:
  -teor-no, needs-design, needs-proposal-maybe,  |
  single-onion   |
Parent ID:  #24962   | Points:  5
 Reviewer:   |Sponsor:
-+-
Changes (by dgoulet):

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


Comment:

 I think the patch would simply looks like this. Nothing final, I just want
 feedback.

 Branch: `ticket17945_033_01`

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #17945 [Core Tor/Tor]: Stop Tor2Web connecting to (Rendezvous) Single Onion Services

[Tor Bug Tracker & Wiki]

#17945: Stop Tor2Web connecting to (Rendezvous) Single Onion Services
-+-
 Reporter:  teor |  Owner:  dgoulet
 Type:  enhancement  | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor2web, tor-hs, 029-proposed, 029   |  Actual Points:
  -teor-no, needs-design, needs-proposal-maybe,  |
  single-onion   |
Parent ID:  #24962   | Points:  5
 Reviewer:   |Sponsor:
-+-
Changes (by dgoulet):

 * status:  accepted => needs_review


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

Re: [tor-bugs] #24166 [Metrics/Library]: Make descriptor reading stoppable

[Tor Bug Tracker & Wiki]

#24166: Make descriptor reading stoppable
-+--
 Reporter:  iwakeh   |  Owner:  metrics-team
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Metrics/Library  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  metrics-2018 |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by iwakeh):

 This relates closely to
 [https://trac.torproject.org/projects/tor/ticket/20395#comment:17 #20395
 comment 17].

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #20395 [Metrics/Library]: Add capability to handle large descriptor files

[Tor Bug Tracker & Wiki]

#20395: Add capability to handle large descriptor files
-+
 Reporter:  iwakeh   |  Owner:  karsten
 Type:  defect   | Status:  needs_revision
 Priority:  Medium   |  Milestone:
Component:  Metrics/Library  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:  iwakeh   |Sponsor:
-+

Comment (by iwakeh):

 Consider also #24166, which would be easily achievable with the suggestion
 in comment:17.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #20395 [Metrics/Library]: Add capability to handle large descriptor files

[Tor Bug Tracker & Wiki]

#20395: Add capability to handle large descriptor files
-+
 Reporter:  iwakeh   |  Owner:  karsten
 Type:  defect   | Status:  needs_revision
 Priority:  Medium   |  Milestone:
Component:  Metrics/Library  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:  iwakeh   |Sponsor:
-+

Comment (by karsten):

 Hmm. I see the benefits of such an API change. And we already have #22678
 that describes something very close, if not the same.

 But should we separate the API change from this fix? In a way, I consider
 it a bug that we're parsing an entire descriptor file before passing all
 descriptors to the application. It's something we should have changed when
 taking out `DescriptorFile`.

 How about I rewrite my patch to not make any changes to the API (in
 particular `DescriptorParser`), and then we discuss the API change,
 including how to do it in a backward-compatible fashion, as part of
 #22678?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25236 [Core Tor/Tor]: dos: Document torrc default values in the man page when not in the consensus

[Tor Bug Tracker & Wiki]

#25236: dos: Document torrc default values in the man page when not in the
consensus
---+---
 Reporter:  dgoulet|  Owner:  dgoulet
 Type:  defect | Status:  needs_review
 Priority:  Medium |  Milestone:  Tor:
   |  0.3.3.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  tor-dos, manpage, tor-doc  |  Actual Points:
Parent ID:  #24902 | Points:
 Reviewer: |Sponsor:
---+---

Comment (by nickm):

 lgtm, if you believe that these assertions can't fail.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25236 [Core Tor/Tor]: dos: Document torrc default values in the man page when not in the consensus

[Tor Bug Tracker & Wiki]

#25236: dos: Document torrc default values in the man page when not in the
consensus
---+---
 Reporter:  dgoulet|  Owner:  dgoulet
 Type:  defect | Status:  needs_review
 Priority:  Medium |  Milestone:  Tor:
   |  0.3.3.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  tor-dos, manpage, tor-doc  |  Actual Points:
Parent ID:  #24902 | Points:
 Reviewer: |Sponsor:
---+---

Comment (by nickm):

 ugh, i looked at the wrong branch. hang on...

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25202 [Core Tor/Tor]: Check the calculations in cc_stats_refill_bucket using non fatal assertions

[Tor Bug Tracker & Wiki]

#25202: Check the calculations in cc_stats_refill_bucket using non fatal 
assertions
+--
 Reporter:  teor|  Owner:  dgoulet
 Type:  defect  | Status:
|  merge_ready
 Priority:  Low |  Milestone:  Tor:
|  0.3.3.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  tor-dos, review-group-32, 033-must  |  Actual Points:
Parent ID:  #24902  | Points:  0.1
 Reviewer:  |Sponsor:
+--
Changes (by nickm):

 * status:  needs_review => merge_ready


Comment:

 lgtm, if you believe that these assertions can't fail.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24707 [Metrics]: Define R coding guidelines for Metrics' products

[Tor Bug Tracker & Wiki]

#24707: Define R coding guidelines for Metrics' products
-+--
 Reporter:  iwakeh   |  Owner:  metrics-team
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Metrics  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by karsten):

 Good idea to define some guidelines. Ideally, we'd even have a checkstyle
 thingy for them.

 Here's a random example from "R for Data Science", which I guess is The R
 Book that we should not ignore:

 {{{
 # Compute rate per 10,000
 table1 %>%
   mutate(rate = cases / population * 1)

 # Compute cases per year
 table1 %>%
   count(year, wt = cases)

 # Visualise changes over time
 library(ggplot2)
 ggplot(table1, aes(year, cases)) +
   geom_line(aes(group = country), colour = "grey50") +
   geom_point(aes(colour = country))
 }}}

 https://github.com/hadley/r4ds/blob/master/tidy.Rmd

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25236 [Core Tor/Tor]: dos: Document torrc default values in the man page when not in the consensus

[Tor Bug Tracker & Wiki]

#25236: dos: Document torrc default values in the man page when not in the
consensus
---+---
 Reporter:  dgoulet|  Owner:  dgoulet
 Type:  defect | Status:  needs_review
 Priority:  Medium |  Milestone:  Tor:
   |  0.3.3.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  tor-dos, manpage, tor-doc  |  Actual Points:
Parent ID:  #24902 | Points:
 Reviewer: |Sponsor:
---+---

Comment (by nickm):

 s/gonsensus/consensus/;

 The documentation for DoSCreationDefenseTimePeriod should use the same
 template as we use for other INTERVAL values, since it accepts units other
 than seconds.

 Otherwise lgtm!

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25236 [Core Tor/Tor]: dos: Document torrc default values in the man page when not in the consensus

[Tor Bug Tracker & Wiki]

#25236: dos: Document torrc default values in the man page when not in the
consensus
---+---
 Reporter:  dgoulet|  Owner:  dgoulet
 Type:  defect | Status:  needs_review
 Priority:  Medium |  Milestone:  Tor:
   |  0.3.3.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  tor-dos, manpage, tor-doc  |  Actual Points:
Parent ID:  #24902 | Points:
 Reviewer: |Sponsor:
---+---

Comment (by nickm):

 (Feel free to merge into ticket24902_029_05 once those issues are
 resolved)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25223 [Core Tor/Tor]: dos: dos_new_client_conn: Non-fatal assertion !(entry == NULL) failed

[Tor Bug Tracker & Wiki]

#25223: dos: dos_new_client_conn: Non-fatal assertion !(entry == NULL) failed
--+
 Reporter:  dgoulet   |  Owner:  dgoulet
 Type:  defect| Status:  merge_ready
 Priority:  High  |  Milestone:  Tor:
  |  0.3.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tor-dos, tor-relay, 033-must  |  Actual Points:
Parent ID:  #24902| Points:
 Reviewer:|Sponsor:
--+
Changes (by nickm):

 * status:  needs_review => merge_ready


Comment:

 lgtm

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25022 [Metrics/Website]: Convert all scripts used for building to Ant tasks

[Tor Bug Tracker & Wiki]

#25022: Convert all scripts used for building to Ant tasks
-+--
 Reporter:  iwakeh   |  Owner:  iwakeh, metrics-team
 Type:  enhancement  | Status:  needs_information
 Priority:  Medium   |  Milestone:
Component:  Metrics/Website  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by karsten):

 No, that's not the issue. awk does reside in `/usr/bin/awk`, and
 commenting out that line doesn't resolve the issue.

 Take a look at the `${generated}` part below. That's an actual directory
 name that was not correctly resolved by Ant.

 {{{
 ~/src/metrics-web$ find . | grep tmp
 ./${generated}/spec/bridge-descriptors.tmp
 ./${generated}/spec/bridge-descriptors.tmp2
 }}}

 Not sure why this works for you. What am I doing wrong?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #20395 [Metrics/Library]: Add capability to handle large descriptor files

[Tor Bug Tracker & Wiki]

#20395: Add capability to handle large descriptor files
-+
 Reporter:  iwakeh   |  Owner:  karsten
 Type:  defect   | Status:  needs_revision
 Priority:  Medium   |  Milestone:
Component:  Metrics/Library  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:  iwakeh   |Sponsor:
-+

Comment (by iwakeh):

 Replying to [comment:19 karsten]:
 > Hmm. I see the benefits of such an API change. And we already have
 #22678 that describes something very close, if not the same.

 Yes!

 >
 > But should we separate the API change from this fix? In a way, I
 consider it a bug that we're parsing an entire descriptor file before
 passing all descriptors to the application. It's something we should have
 changed when taking out `DescriptorFile`.
 >
 > How about I rewrite my patch to not make any changes to the API (in
 particular `DescriptorParser`), and then we discuss the API change,
 including how to do it in a backward-compatible fashion, as part of
 #22678?

 I think all effort is better spent renewing the API.  You might name the
 issue at hand a 'bug', but it really is not.  The issues we're dealing
 with are historically grown design decisions that should be modernized
 now, not patched and stitched to last longer.  There is no way around the
 API change, so the sooner the better.

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

Re: [tor-bugs] #25022 [Metrics/Website]: Convert all scripts used for building to Ant tasks

[Tor Bug Tracker & Wiki]

#25022: Convert all scripts used for building to Ant tasks
-+--
 Reporter:  iwakeh   |  Owner:  iwakeh, metrics-team
 Type:  enhancement  | Status:  needs_information
 Priority:  Medium   |  Milestone:
Component:  Metrics/Website  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by karsten):

 * cc: metrics-team (added)


Comment:

 Please leave metrics-team in cc. Otherwise I don't get notifications.
 Argh, Trac.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #20395 [Metrics/Library]: Add capability to handle large descriptor files

[Tor Bug Tracker & Wiki]

#20395: Add capability to handle large descriptor files
-+
 Reporter:  iwakeh   |  Owner:  karsten
 Type:  defect   | Status:  needs_revision
 Priority:  Medium   |  Milestone:
Component:  Metrics/Library  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:  iwakeh   |Sponsor:
-+

Comment (by karsten):

 I think the two issues are unrelated. One is about adding parsed
 descriptors to a data structure, the other is about using different code
 for the data structure.

 Let's just try to fix this in the next couple of days. If that includes a
 backward-compatible API change, that's okay. Want to grab 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] #24432 [Obfuscation/BridgeDB]: The meek<->moat tunneling isn't set up correctly

[Tor Bug Tracker & Wiki]

#24432: The meek<->moat tunneling isn't set up correctly
--+--
 Reporter:  isis  |  Owner:  isis
 Type:  defect| Status:  reopened
 Priority:  High  |  Milestone:
Component:  Obfuscation/BridgeDB  |Version:
 Severity:  Normal| Resolution:
 Keywords:  moat bridgedb-dist|  Actual Points:
Parent ID:  #24689| Points:  2
 Reviewer:|Sponsor:  SponsorM
--+--

Comment (by mcs):

 Replying to [comment:25 isis]:
 >  3. The moat server is erroring with `415 Unsupported Media Type`, but
 that would only happen if it got the HTTP header `Content-Type:
 application/vnd.api+json` but with a media type parameter specified, e.g.
 `Content-Type: application/vnd.api+json;jpeg`. (So it sounds like either
 Apache, the meek reflector, or meek-server is altering the headers?)

 I found a typo in your `moat-fetch-and-format-captcha-response.py` script
 :)
 There is a missing comma at the end of this line:
  '--proxy', 'socks5://127.0.0.1:1/'
 I also had to remove the extra quotes around the header values.

 After I fixed those problems, I always receive a "The CAPTCHA solution was
 incorrect." response (even though I am trying really hard to provide the
 correct answer). With Tor Launcher we still see the "No bridges available
 to fulfill request: None." response, so maybe there is another problem
 with the test script. I did notice that the data "payload" was not
 enclosed in square brackets, but fixing that made no difference.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25022 [Metrics/Website]: Convert all scripts used for building to Ant tasks

[Tor Bug Tracker & Wiki]

#25022: Convert all scripts used for building to Ant tasks
-+--
 Reporter:  iwakeh   |  Owner:  iwakeh, metrics-team
 Type:  enhancement  | Status:  needs_information
 Priority:  Medium   |  Milestone:
Component:  Metrics/Website  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by iwakeh):

 Replying to [comment:8 karsten]:
 > No, that's not the issue. awk does reside in `/usr/bin/awk`, and
 commenting out that line doesn't resolve the issue.
 >
 > Take a look at the `${generated}` part below. That's an actual directory
 name that was not correctly resolved by Ant.

 Good point!

 >...
 > Not sure why this works for you. What am I doing wrong?

 Did you run the bootstrap script?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25231 [Metrics/Website]: Restore metrics-lib submodule in metrics-web

[Tor Bug Tracker & Wiki]

#25231: Restore metrics-lib submodule in metrics-web
-+--
 Reporter:  iwakeh   |  Owner:  iwakeh
 Type:  defect   | Status:  needs_review
 Priority:  High |  Milestone:
Component:  Metrics/Website  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:  karsten  |Sponsor:
-+--

Comment (by karsten):

 Oops. I'll take a look 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] #20395 [Metrics/Library]: Add capability to handle large descriptor files

[Tor Bug Tracker & Wiki]

#20395: Add capability to handle large descriptor files
-+--
 Reporter:  iwakeh   |  Owner:  iwakeh
 Type:  defect   | Status:  accepted
 Priority:  Medium   |  Milestone:
Component:  Metrics/Library  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:  iwakeh   |Sponsor:
-+--
Changes (by iwakeh):

 * status:  needs_revision => accepted
 * owner:  karsten => iwakeh


Comment:

 I'll give it try.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24775 [Core Tor/Tor]: Reduce "Channel padding timeout scheduled" NOTICE messages

[Tor Bug Tracker & Wiki]

#24775: Reduce "Channel padding timeout scheduled" NOTICE messages
-+-
 Reporter:  Dbryrtfbcbhgf|  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  032-backport, 031-backport,  |  Actual Points:
  033-must   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by cypherpunks):

 I've just got this message in my tor client log files, 0.3.2.9 (I don't
 run tor node):

 `[notice] Channel padding timeout scheduled XXms in the past`

 Nothing suspicious was written in logs before or after that. I don't thing
 my time clock has experienced big jump.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #22660 [Core Tor/Tor]: Guard against stack smashing attacks in tor with additional compiler options.

[Tor Bug Tracker & Wiki]

#22660: Guard against stack smashing attacks in tor with additional compiler
options.
-+-
 Reporter:  teor |  Owner:  nickm
 Type:  defect   | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.4.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-hardening, security, |  Actual Points:
  029-backport, 031-backport, 032-backport,  |
  033-backport, review-group-19, 032-unreached   |
Parent ID:   | Points:  0.5
 Reviewer:   |Sponsor:
-+-
Changes (by cypherpunks):

 * keywords:
 tor-hardening, security, 029-backport, 031-backport, review-group-19,
 032-unreached
 =>
 tor-hardening, security, 029-backport, 031-backport, 032-backport,
 033-backport, review-group-19, 032-unreached
 * milestone:  Tor: unspecified => Tor: 0.3.4.x-final


Comment:

 Hardening is useful.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24432 [Obfuscation/BridgeDB]: The meek<->moat tunneling isn't set up correctly

[Tor Bug Tracker & Wiki]

#24432: The meek<->moat tunneling isn't set up correctly
--+--
 Reporter:  isis  |  Owner:  isis
 Type:  defect| Status:  reopened
 Priority:  High  |  Milestone:
Component:  Obfuscation/BridgeDB  |Version:
 Severity:  Normal| Resolution:
 Keywords:  moat bridgedb-dist|  Actual Points:
Parent ID:  #24689| Points:  2
 Reviewer:|Sponsor:  SponsorM
--+--

Comment (by mcs):

 One more follow up: Kathy and I experimented a little bit with Tor
 Launcher. When communicating with the production BridgeDB server, if we
 include square brackets around the data payload in the `check` request we
 receive a "No bridges available to fulfill request: None." error. If we
 omit the square brackets, we always receive a "The CAPTCHA solution was
 incorrect." error.

 I know we talked about the square brackets / array issue before, at least
 in the context of the JSON responses. Including the brackets in the
 requests makes things work completely when we use a BridgeDB test server
 that we built ourselves (i.e., bridges are returned). But let us know what
 we should be doing, or we can look at your test scripts once they are
 working.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #21969 [Core Tor/Tor]: We're missing descriptors for some of our primary entry guards

[Tor Bug Tracker & Wiki]

#21969: We're missing descriptors for some of our primary entry guards
-+-
 Reporter:  asn  |  Owner:  asn
 Type:  defect   | Status:  new
 Priority:  Immediate|  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.0.6
 Severity:  Blocker  | Resolution:
 Keywords:  tor-guard, tor-bridge, tor-client,   |  Actual Points:
  tbb-usability-website, tbb-needs   |
Parent ID:   | Points:  1.5
 Reviewer:   |Sponsor:
 |  SponsorV
-+-
Changes (by cypherpunks):

 * cc: cypherpunks (removed)
 * keywords:  tor-guard, tor-bridge, tor-client => tor-guard, tor-bridge,
 tor-client, tbb-usability-website, tbb-needs
 * status:  needs_information => new
 * milestone:  Tor: 0.3.4.x-final => Tor: 0.3.3.x-final


Comment:

 comment:61 is correct. If you say tor gets out of that state in seconds
 now, then it should clear its leftovers (stalled circuits/state/etc) right
 thereafter.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25236 [Core Tor/Tor]: dos: Document torrc default values in the man page when not in the consensus

[Tor Bug Tracker & Wiki]

#25236: dos: Document torrc default values in the man page when not in the
consensus
---+---
 Reporter:  dgoulet|  Owner:  dgoulet
 Type:  defect | Status:  needs_review
 Priority:  Medium |  Milestone:  Tor:
   |  0.3.3.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  tor-dos, manpage, tor-doc  |  Actual Points:
Parent ID:  #24902 | Points:
 Reviewer: |Sponsor:
---+---

Comment (by dgoulet):

 Replying to [comment:4 nickm]:
 > s/gonsensus/consensus/;
 >
 > The documentation for DoSCreationDefenseTimePeriod should use the same
 template as we use for other INTERVAL values, since it accepts units other
 than seconds.

 Wait it does not. It is a flat number of seconds. Maybe you got confused
 with the `1 hour` ... I'm removing it.

 >
 > Otherwise lgtm!

 See fixup commit: `3ff67e802c`

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25238 [Metrics/Relay Search]: Can't list all relays for a version when aggregating by version

[Tor Bug Tracker & Wiki]

#25238: Can't list all relays for a version when aggregating by version
--+--
 Reporter:  irl   |  Owner:  metrics-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Metrics/Relay Search  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 This is probably just something missed out in the template. Guards/Exits
 are clickable but Relays are not.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25236 [Core Tor/Tor]: dos: Document torrc default values in the man page when not in the consensus

[Tor Bug Tracker & Wiki]

#25236: dos: Document torrc default values in the man page when not in the
consensus
---+---
 Reporter:  dgoulet|  Owner:  dgoulet
 Type:  defect | Status:  needs_review
 Priority:  Medium |  Milestone:  Tor:
   |  0.3.3.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  tor-dos, manpage, tor-doc  |  Actual Points:
Parent ID:  #24902 | Points:
 Reviewer: |Sponsor:
---+---

Comment (by nickm):

 But it says this:
 {{{
   V(DoSCircuitCreationDefenseTimePeriod,   INTERVAL, "0"),
 }}}

 That means that `DoSCircuitCreationDefenseTimePeriod 1 hour` should work.
 And in my tests, it does!

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25223 [Core Tor/Tor]: dos: dos_new_client_conn: Non-fatal assertion !(entry == NULL) failed

[Tor Bug Tracker & Wiki]

#25223: dos: dos_new_client_conn: Non-fatal assertion !(entry == NULL) failed
--+
 Reporter:  dgoulet   |  Owner:  dgoulet
 Type:  defect| Status:  closed
 Priority:  High  |  Milestone:  Tor:
  |  0.3.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:  tor-dos, tor-relay, 033-must  |  Actual Points:
Parent ID:  #24902| Points:
 Reviewer:  nickm |Sponsor:
--+
Changes (by dgoulet):

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


Comment:

 Merged into #24902.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25202 [Core Tor/Tor]: Check the calculations in cc_stats_refill_bucket using non fatal assertions

[Tor Bug Tracker & Wiki]

#25202: Check the calculations in cc_stats_refill_bucket using non fatal 
assertions
+--
 Reporter:  teor|  Owner:  dgoulet
 Type:  defect  | Status:  closed
 Priority:  Low |  Milestone:  Tor:
|  0.3.3.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:  fixed
 Keywords:  tor-dos, review-group-32, 033-must  |  Actual Points:
Parent ID:  #24902  | Points:  0.1
 Reviewer:  nickm   |Sponsor:
+--
Changes (by dgoulet):

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


Comment:

 Merged into #24902.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25239 [Metrics/Relay Search]: Link to server descriptor and extra info descriptor when relays have a DirPort

[Tor Bug Tracker & Wiki]

#25239: Link to server descriptor and extra info descriptor when relays have a
DirPort
--+--
 Reporter:  irl   |  Owner:  metrics-team
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Metrics/Relay Search  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 A stop gap measure on the path to #22026.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25236 [Core Tor/Tor]: dos: Document torrc default values in the man page when not in the consensus

[Tor Bug Tracker & Wiki]

#25236: dos: Document torrc default values in the man page when not in the
consensus
---+---
 Reporter:  dgoulet|  Owner:  dgoulet
 Type:  defect | Status:  needs_review
 Priority:  Medium |  Milestone:  Tor:
   |  0.3.3.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  tor-dos, manpage, tor-doc  |  Actual Points:
Parent ID:  #24902 | Points:
 Reviewer: |Sponsor:
---+---

Comment (by dgoulet):

 Oh oh! Well that is great! How does that look?

 Here is a new fixup: `2a16d0a9c2`

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25034 [Metrics/Relay Search]: inconsistent eff. family counter in Relay Search

[Tor Bug Tracker & Wiki]

#25034: inconsistent eff. family counter in Relay Search
--+--
 Reporter:  cypherpunks   |  Owner:  metrics-team
 Type:  defect| Status:  new
 Priority:  Low   |  Milestone:
Component:  Metrics/Relay Search  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by irl):

 Am I understanding correctly that the effective family was including the
 fingerprint of the relay itself causing the number to be one more than it
 should have been?

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