Re: [tor-bugs] #24658 [Core Tor/Tor]: Split/refactor crypto.h into smaller separate modules

2018-01-24 Thread Tor Bug Tracker & Wiki
#24658: Split/refactor crypto.h into smaller separate modules
-+-
 Reporter:  isis |  Owner:  (none)
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-crypto, refactor, review-|  Actual Points:
  group-29   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor8-can
-+-
Changes (by nickm):

 * status:  needs_review => new


Comment:

 Merged that too; thanks!

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

Re: [tor-bugs] #16513 [Metrics/Onionoo]: Make writing of the out/ directory from the status/ directory deterministic

2018-01-24 Thread Tor Bug Tracker & Wiki
#16513: Make writing of the out/ directory from the status/ directory 
deterministic
-+---
 Reporter:  karsten  |  Owner:  iwakeh
 Type:  enhancement  | Status:  accepted
 Priority:  High |  Milestone:  Onionoo-2.0.0
Component:  Metrics/Onionoo  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  metrics-2018 |  Actual Points:
Parent ID:   | Points:
 Reviewer:  iwakeh   |Sponsor:
-+---

Comment (by iwakeh):

 Replying to [comment:37 karsten]:
 > Replying to [comment:36 iwakeh]:
 > > The list of exit_addresses is one more data item in onionoo's details
 documents that is depending on the current system time.  Depending on the
 current time the addresses are added or omitted to the stored collection
 (cf.
 
[https://gitweb.torproject.org/user/karsten/onionoo.git/tree/src/main/java/org/torproject/onionoo/updater/NodeDetailsStatusUpdater.java?h=task-16513-2#n805
 NodeDetailsStatusUpdater]).  Could the validAfter time of the latest
 consensus processed be a replacement for the system time?
 >
 > Yes. We should probably do that. I haven't tried it out yet, nor have I
 looked around for similar places where we're depending on system time
 there.
 >
 > However! That's a different issue. It's about making the '''update'''
 step less dependent on things like system time, though we won't be able to
 make it fully deterministic. Still a good thing to do. But it's different
 from making the '''write''' step deterministic where we're taking a
 `status/` directory as input and writing files to the `out/` directory.
 Should we collect this idea on a new ticket, like, "Make updating status
 files independent of system time"?

 Oh, I took this ticket as meaning 'Make results from Onionoo
 deterministic', but writing and updating are different concerns.  Will
 open a new ticket (rather with the meaning I perceived) and check for more
 issues in the update process while continuing the 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

[tor-bugs] #25001 [Internal Services/Tor Sysadmin Team]: Refresh gpg key for boklm

2018-01-24 Thread Tor Bug Tracker & Wiki
#25001: Refresh gpg key for boklm
-+-
 Reporter:  boklm|  Owner:  tpa
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 {{{
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA256

 Please refresh key 3E39CEABFC69F6F7 in order to update subkeys expiration
 date.

 Thanks
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v2

 iQIcBAEBCAAGBQJaaKSgAAoJEAe3z9eg+6BilN0P/2rmdtHXSWRHpR6aKoIPH/7o
 DM7PDkC2epaL/291Jobhy/zjiZWPKdepGMci1Ulu5mSlj3yDmlD6xx0VlVCmY+Lo
 Ayt+ZMERq7bsf4EHzK8Q1Iz25gdiIfzI97D+P6I7QXuiw4t/uEoT4wZ+PnhrPNQ+
 rBqTvm5hfNjkcD12abAYSYS/RpiA1O02cXlXNMmsJQndzEFInUeNyfOSGqem7evN
 5hoezKMhzu1h9Aql8O3EldhsQgWETSfWM3USzz0LjRBX78XFeaoCSII2Ka8QFrJH
 1cU9FjZAOMpU5iD6DRFNODnob5LmeREol0OchIGBirsSHUQWk+60q7CrmPSbYy6X
 6LOionsyFeOTALhVgfqSog5sqNloRBA7Wq2KTAn85hKFVbCZRSWxnAuy7Ev1TlDl
 nKkv38RcGsd26UYcEG6bTNgo8f+rtytvaE4sLgjBPzEKKL0R6NkH0WdImlDTtBt0
 nG5OTeIO9G244Kg+fwhrZr59P/FUWZNnLr4HRCYKhEpfuU11f/5xAv/7V7uYGJmP
 tLgkw1JqiQ+LDs/XUhcRoagmNF3oe/a/4XYBDo5IpP1JvNARBmKPLRG4GVf2w+AZ
 Djz1vK0VspmwZREFcEgxKXxFoDZk+VPtyq6w2/m5Q9Izk6RrnfTdLmhOsZDr/AV1
 vMW8Km3pIRbJA3b18hBU
 =a8F6
 -END PGP SIGNATURE-
 }}}

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

Re: [tor-bugs] #24996 [Metrics/Statistics]: OnionPerf showing >200% timeouts

2018-01-24 Thread Tor Bug Tracker & Wiki
#24996: OnionPerf showing >200% timeouts
+--
 Reporter:  irl |  Owner:  karsten
 Type:  defect  | Status:  accepted
 Priority:  Medium  |  Milestone:
Component:  Metrics/Statistics  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by karsten):

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


Comment:

 True. I'll take a look.

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

Re: [tor-bugs] #16513 [Metrics/Onionoo]: Make writing of the out/ directory from the status/ directory deterministic

2018-01-24 Thread Tor Bug Tracker & Wiki
#16513: Make writing of the out/ directory from the status/ directory 
deterministic
-+---
 Reporter:  karsten  |  Owner:  iwakeh
 Type:  enhancement  | Status:  accepted
 Priority:  High |  Milestone:  Onionoo-2.0.0
Component:  Metrics/Onionoo  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  metrics-2018 |  Actual Points:
Parent ID:   | Points:
 Reviewer:  iwakeh   |Sponsor:
-+---

Comment (by karsten):

 Replying to [comment:36 iwakeh]:
 > The list of exit_addresses is one more data item in onionoo's details
 documents that is depending on the current system time.  Depending on the
 current time the addresses are added or omitted to the stored collection
 (cf.
 
[https://gitweb.torproject.org/user/karsten/onionoo.git/tree/src/main/java/org/torproject/onionoo/updater/NodeDetailsStatusUpdater.java?h=task-16513-2#n805
 NodeDetailsStatusUpdater]).  Could the validAfter time of the latest
 consensus processed be a replacement for the system time?

 Yes. We should probably do that. I haven't tried it out yet, nor have I
 looked around for similar places where we're depending on system time
 there.

 However! That's a different issue. It's about making the '''update''' step
 less dependent on things like system time, though we won't be able to make
 it fully deterministic. Still a good thing to do. But it's different from
 making the '''write''' step deterministic where we're taking a `status/`
 directory as input and writing files to the `out/` directory. Should we
 collect this idea on a new ticket, like, "Make updating status files
 independent of system time"?

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

Re: [tor-bugs] #22176 [Applications/Tor Browser]: Review networking code for Firefox 60 (was: Review networking code for Firefox 59)

2018-01-24 Thread Tor Bug Tracker & Wiki
#22176: Review networking code for Firefox 60
--+--
 Reporter:  gk|  Owner:  tbb-team
 Type:  task  | Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ff60-esr  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by gk):

 * keywords:  ff59-esr => ff60-esr
 * priority:  Very High => Medium
 * severity:  Critical => Normal


Old description:

> We should review the networking code for Firefox 59 to make sure the are
> no Tor bypasses.

New description:

 We should review the networking code for Firefox 60 to make sure the are
 no Tor bypasses.

--

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

[tor-bugs] [Tor Bug Tracker & Wiki] Batch modify: #14952, #15563, #16339, #18598, ...

2018-01-24 Thread Tor Bug Tracker & Wiki
Batch modification to #14952, #15563, #16339, #18598, #18599, #18862, #21777, 
#21785, #21787, #22971, #23424, #9898, #12968, #15910, #16149, #16285, #16693, 
#18560, #19004, #21549, #21607, #21687, #21770, #21793, #22074, #22166, #23317, 
#23362, #23392, #23451, #23489, #23547, #23649, #23805, #24539, #24553, #24631, 
#24632, #24648, #24686, #22162 by gk:


Comment:
Firefox 60 is the new ESR.

--
Tickets URL: 

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

Re: [tor-bugs] #24980 [Webpages]: Add QubesOS and Whonix's next-gen onion services

2018-01-24 Thread Tor Bug Tracker & Wiki
#24980: Add QubesOS and Whonix's next-gen onion services
-+-
 Reporter:  cypherpunks  |  Owner:  asn
 Type:  task | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Webpages |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:   |  Actual Points:
Parent ID:   | Points:  0.000231481
 Reviewer:   |Sponsor:
-+-

Comment (by cypherpunks):

 Also I forgot please replace

 {{{
  You will need a Tor browser running at least tor-0.3.2.1-alpha (e.g. Tor
 Browser 7.5a5) to visit these:
 }}}

 with


 {{{
  You will need the latest Tor Browser stable (7.5) or alpha to visit
 these:
 }}}

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

Re: [tor-bugs] #24672 [Community/Tor Browser Manual]: The Security Slider manual should reflect the new changes mad to the security slider

2018-01-24 Thread Tor Bug Tracker & Wiki
#24672: The Security Slider manual should reflect the new changes mad to the
security slider
--+---
 Reporter:  Dbryrtfbcbhgf |  Owner:  phoul
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Community/Tor Browser Manual  |Version:
 Severity:  Minor | Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---
Changes (by boklm):

 * priority:  Low => Medium


Comment:

 The new stable release now includes the new security slider, so it might
 be a good time to update the manual.

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

Re: [tor-bugs] #24672 [Community/Tor Browser Manual]: The Security Slider manual should reflect the new changes mad to the security slider

2018-01-24 Thread Tor Bug Tracker & Wiki
#24672: The Security Slider manual should reflect the new changes mad to the
security slider
--+---
 Reporter:  Dbryrtfbcbhgf |  Owner:  phoul
 Type:  defect| Status:  new
 Priority:  Low   |  Milestone:
Component:  Community/Tor Browser Manual  |Version:
 Severity:  Minor | Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---
Changes (by boklm):

 * owner:  (none) => phoul
 * component:  Webpages/Website => Community/Tor Browser Manual


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

Re: [tor-bugs] #24992 [Core Tor/Tor]: SingleOnion (and Tor2web?) connections may need better expiry, lots left open

2018-01-24 Thread Tor Bug Tracker & Wiki
#24992: SingleOnion (and Tor2web?) connections may need better expiry, lots left
open
---+--
 Reporter:  alecmuffett|  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Core Tor/Tor   |Version:  Tor: 0.3.2.9
 Severity:  Normal | Resolution:
 Keywords:  singleonion, circuits  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--

Comment (by alecmuffett):

 I'm setting up a dozen worker single-onions using the same config as this
 bug; two of them have complained at-startup, with the logs recording
 messages like this, which might be relevant to the large numbers of
 circuits being open.

 {{{
 Jan 24 13:17:35.000 [notice] Tor has successfully opened a circuit. Looks
 like client functionality is working.
 Jan 24 13:17:35.000 [notice] Bootstrapped 100%: Done
 Jan 24 13:19:49.000 [warn] Hidden service [scrubbed] exceeded launch limit
 with 10 intro points in the last 180 seconds. Intro circuit launches are
 limited to 10 per 300 seconds.
 Jan 24 13:19:49.000 [warn] Service configured in
 "/home/pi/eotk/projects.d/x.d/hs-2.d":
 Jan 24 13:19:49.000 [warn]   Intro point 0 at [scrubbed]: circuit is open
 Jan 24 13:19:49.000 [warn]   Intro point 1 at [scrubbed]: circuit is open
 Jan 24 13:19:49.000 [warn]   Intro point 2 at [scrubbed]: circuit is open
 Jan 24 13:25:15.000 [warn] Hidden service [scrubbed] exceeded launch limit
 with 10 intro points in the last 205 seconds. Intro circuit launches are
 limited to 10 per 300 seconds. [121 similar message(s) suppressed in last
 300 seconds]
 Jan 24 13:25:15.000 [warn] Service configured in
 "/home/pi/eotk/projects.d/x.d/hs-2.d":
 Jan 24 13:25:15.000 [warn]   Intro point 0 at [scrubbed]: circuit is open
 Jan 24 13:25:15.000 [warn]   Intro point 1 at [scrubbed]: circuit is open
 Jan 24 13:25:15.000 [warn]   Intro point 2 at [scrubbed]: circuit is open
 }}}

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

Re: [tor-bugs] #16513 [Metrics/Onionoo]: Make writing of the out/ directory from the status/ directory deterministic

2018-01-24 Thread Tor Bug Tracker & Wiki
#16513: Make writing of the out/ directory from the status/ directory 
deterministic
-+---
 Reporter:  karsten  |  Owner:  iwakeh
 Type:  enhancement  | Status:  accepted
 Priority:  High |  Milestone:  Onionoo-2.0.0
Component:  Metrics/Onionoo  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  metrics-2018 |  Actual Points:
Parent ID:   | Points:
 Reviewer:  iwakeh   |Sponsor:
-+---

Comment (by iwakeh):

 The list of exit_addresses is one more data item in onionoo's details
 documents that is depending on the current system time.  Depending on the
 current time the addresses are added or omitted to the stored collection
 (cf.
 
[https://gitweb.torproject.org/user/karsten/onionoo.git/tree/src/main/java/org/torproject/onionoo/updater/NodeDetailsStatusUpdater.java?h=task-16513-2#n805
 NodeDetailsStatusUpdater]).  Could the validAfter time of the currently
 processed consensus be a replacement for the system time?

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

Re: [tor-bugs] #24980 [Webpages]: Add QubesOS and Whonix's next-gen onion services

2018-01-24 Thread Tor Bug Tracker & Wiki
#24980: Add QubesOS and Whonix's next-gen onion services
-+-
 Reporter:  cypherpunks  |  Owner:  asn
 Type:  task | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Webpages |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:   |  Actual Points:
Parent ID:   | Points:  0.000231481
 Reviewer:   |Sponsor:
-+-
Changes (by asn):

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


Comment:

 Thanks for the heads-up. Done! :)
 Also added a link to the page so that there is some sort of
 verification...

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25000 [Applications/Tor Browser]: TorBrowser's NoScript is breaking add-on system

2018-01-24 Thread Tor Bug Tracker & Wiki
#25000: TorBrowser's NoScript is breaking add-on system
--+--
 Reporter:  cypherpunks   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 https://forums.informaction.com/viewtopic.php?f=7=24484=HELLO

 Just try it. Tested by myself.

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

Re: [tor-bugs] #24217 [Metrics/Statistics]: Specify data format and aggregation process of new IPv6 relay statistics

2018-01-24 Thread Tor Bug Tracker & Wiki
#24217: Specify data format and aggregation process of new IPv6 relay statistics
+--
 Reporter:  karsten |  Owner:  karsten
 Type:  enhancement | Status:  needs_review
 Priority:  High|  Milestone:
Component:  Metrics/Statistics  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  iwakeh  |Sponsor:
+--

Comment (by karsten):

 Thanks, iwakeh!

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

Re: [tor-bugs] #24980 [Webpages]: Add QubesOS and Whonix's next-gen onion services

2018-01-24 Thread Tor Bug Tracker & Wiki
#24980: Add QubesOS and Whonix's next-gen onion services
-+-
 Reporter:  cypherpunks  |  Owner:  asn
 Type:  task | Status:  assigned
 Priority:  Medium   |  Milestone:
Component:  Webpages |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:  0.000231481
 Reviewer:   |Sponsor:
-+-
Changes (by cypherpunks):

 * points:   => 0.000231481


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

Re: [tor-bugs] #24217 [Metrics/Statistics]: Specify data format and aggregation process of new IPv6 relay statistics

2018-01-24 Thread Tor Bug Tracker & Wiki
#24217: Specify data format and aggregation process of new IPv6 relay statistics
+--
 Reporter:  karsten |  Owner:  karsten
 Type:  enhancement | Status:  needs_review
 Priority:  High|  Milestone:
Component:  Metrics/Statistics  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  iwakeh  |Sponsor:
+--
Changes (by iwakeh):

 * reviewer:   => iwakeh


Comment:

 Cool!
 Adding myself to the reviewer field for reference (and assuming that other
 can add their username there, too).
 Trying to get a first feedback done before tomorrows team-meeting.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: 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

2018-01-24 Thread Tor Bug Tracker & Wiki
#24902: Denial of Service mitigation subsystem
-+-
 Reporter:  dgoulet  |  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:  ddos, tor-relay, review-group-30,|  Actual Points:
  029-backport, 031-backport, 032-backport   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by asn):

 Please check branch `ticket24902_refill_test` in my repo for another
 unittest, testing the token bucket refill procedure! Cheers!

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

Re: [tor-bugs] #24983 [Metrics/CollecTor]: Inaccessible semi-recent consensus files

2018-01-24 Thread Tor Bug Tracker & Wiki
#24983: Inaccessible semi-recent consensus files
---+--
 Reporter:  robgjansen |  Owner:  karsten
 Type:  defect | Status:  accepted
 Priority:  Medium |  Milestone:
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--

Comment (by karsten):

 So, it looks like the files from January 19 are still not available,
 because the cronjob on January 22 was interrupted by a server reboot. The
 next regular run would start tomorrow on January 25.

 I changed the cronjob from every 3 days to every 2 days. And I triggered a
 manual run which should finish some time this evening (UTC). The next
 cronjob will start at 03:25 UTC tonight.

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

Re: [tor-bugs] #24217 [Metrics/Statistics]: Specify data format and aggregation process of new IPv6 relay statistics

2018-01-24 Thread Tor Bug Tracker & Wiki
#24217: Specify data format and aggregation process of new IPv6 relay statistics
+--
 Reporter:  karsten |  Owner:  karsten
 Type:  enhancement | Status:  accepted
 Priority:  High|  Milestone:
Component:  Metrics/Statistics  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by karsten):

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


Comment:

 I guess I should accept the ticket, as I'll likely going to be working on
 it over the next week.

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

Re: [tor-bugs] #24217 [Metrics/Statistics]: Specify data format and aggregation process of new IPv6 relay statistics

2018-01-24 Thread Tor Bug Tracker & Wiki
#24217: Specify data format and aggregation process of new IPv6 relay statistics
+--
 Reporter:  karsten |  Owner:  karsten
 Type:  enhancement | Status:  needs_review
 Priority:  High|  Milestone:
Component:  Metrics/Statistics  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by karsten):

 * 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] #24217 [Metrics/Statistics]: Specify data format and aggregation process of new IPv6 relay statistics

2018-01-24 Thread Tor Bug Tracker & Wiki
#24217: Specify data format and aggregation process of new IPv6 relay statistics
+--
 Reporter:  karsten |  Owner:  metrics-team
 Type:  enhancement | Status:  needs_review
 Priority:  High|  Milestone:
Component:  Metrics/Statistics  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by karsten):

 * status:  new => needs_review
 * priority:  Medium => High


Comment:

 I made a start here by writing a draft for graphs in the Servers section
 of Tor Metrics. I did not bother with format and simply picked `.md` for
 now, with a script to convert that to `.html` for easier reading.

 I also came up with a different content structure, based on thinking a bit
 more about what would be doable and what would actually help the intended
 audience. It's supposed to be a start, with a lot of room left for future
 improvement. Don't be shy, I'm open to suggestions.

 Please review this [https://people.torproject.org/~karsten/volatile
 /reproducible-metrics.html first draft]. The source `.md` file is
 available for download [https://people.torproject.org/~karsten/volatile
 /reproducible-metrics.md here] and under version control
 [https://gitweb.torproject.org/karsten/metrics-web.git/log/?h=task-24217
 in my metrics-web task-24217 branch].

 Setting priority to high, because we'd ideally publish a draft of this by
 the end of the month to show that we're making real progress on this
 sponsor deliverable.

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

Re: [tor-bugs] #24857 [Core Tor/Tor]: tor 0.3.1.9 100% cpu load

2018-01-24 Thread Tor Bug Tracker & Wiki
#24857: tor 0.3.1.9 100% cpu load
-+--
 Reporter:  Eugene646|  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Core Tor/Tor |Version:  Tor: 0.3.2.9
 Severity:  Normal   | Resolution:
 Keywords:  cpu, windows, linux  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by creideiki):

 * keywords:  cpu, windows => cpu, windows, linux
 * status:  needs_information => new
 * version:  Tor: 0.3.1.9 => Tor: 0.3.2.9


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

Re: [tor-bugs] #24999 [Applications/Tor Browser]: *.tar.gz debug files are not hashed

2018-01-24 Thread Tor Bug Tracker & Wiki
#24999: *.tar.gz debug files are not hashed
+--
 Reporter:  gk  |  Owner:  tbb-team
 Type:  defect  | Status:  closed
 Priority:  Medium  |  Milestone:
Component:  Applications/Tor Browser|Version:
 Severity:  Normal  | Resolution:  fixed
 Keywords:  tbb-rbm, TorBrowserTeam201801R  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by boklm):

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


Comment:

 This patch looks good to me. I pushed it to `master` as commit
 d2dee352354ee77cd26ac37bef41322df2729ff8 and cherry-picked it to
 `maint-7.5` as commit 7dfd54aab191dfc1b55250569e45840d589f7caf.

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

Re: [tor-bugs] #24717 [Metrics/Bot]: Improve design of relay and bridge badges and map overlay

2018-01-24 Thread Tor Bug Tracker & Wiki
#24717: Improve design of relay and bridge badges and map overlay
-+--
 Reporter:  irl  |  Owner:  antonela
 Type:  enhancement  | Status:  assigned
 Priority:  Medium   |  Milestone:
Component:  Metrics/Bot  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ux-team  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by antonela):

 @irl

 I included an updated version of the map using the Mollweide projection.

 
!https://trac.torproject.org/projects/tor/attachment/ticket/24717/Map%402x--.png

 Do you think we need the Tor Project icon to legitimize it? Maybe should
 we use the TorMetrics one?

 I'm not sure, is up to you :)

 Will wait for your feedback on it.

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

Re: [tor-bugs] #24999 [Applications/Tor Browser]: *.tar.gz debug files are not hashed

2018-01-24 Thread Tor Bug Tracker & Wiki
#24999: *.tar.gz debug files are not hashed
+--
 Reporter:  gk  |  Owner:  tbb-team
 Type:  defect  | Status:  needs_review
 Priority:  Medium  |  Milestone:
Component:  Applications/Tor Browser|Version:
 Severity:  Normal  | Resolution:
 Keywords:  tbb-rbm, TorBrowserTeam201801R  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by gk):

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


Comment:

 `bug_24999` (https://gitweb.torproject.org/user/gk/tor-browser-
 build.git/commit/?h=bug_24999=d2dee352354ee77cd26ac37bef41322df2729ff8)
 in my public `tor-browser-build` directory has a possible 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] #24717 [Metrics/Bot]: Improve design of relay and bridge badges and map overlay

2018-01-24 Thread Tor Bug Tracker & Wiki
#24717: Improve design of relay and bridge badges and map overlay
-+--
 Reporter:  irl  |  Owner:  antonela
 Type:  enhancement  | Status:  assigned
 Priority:  Medium   |  Milestone:
Component:  Metrics/Bot  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ux-team  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by antonela):

 * Attachment "m...@2x--.png" added.


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

[tor-bugs] #24999 [Applications/Tor Browser]: *.tar.gz debug files are not hashed

2018-01-24 Thread Tor Bug Tracker & Wiki
#24999: *.tar.gz debug files are not hashed
--+--
 Reporter:  gk|  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:|
--+--
 When doing release builds I noticed that our debug files (*.tar.gz) are
 not hashed.

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

Re: [tor-bugs] #24995 [Applications/Tor Browser]: Truncated git hash not available in the windows expert bundle build for Tor 0.3.2.9

2018-01-24 Thread Tor Bug Tracker & Wiki
#24995: Truncated git hash not available in the windows expert bundle build for 
Tor
0.3.2.9
--+--
 Reporter:  TheDcoder |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-rbm   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by gk):

 * keywords:   => tbb-rbm
 * version:  Tor: 0.3.2.9 =>


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

Re: [tor-bugs] #24524 [Internal Services/Tor Sysadmin Team]: Please create LDAP access for Richard

2018-01-24 Thread Tor Bug Tracker & Wiki
#24524: Please create LDAP access for Richard
-+-
 Reporter:  ewyatt   |  Owner:  tpa
 Type:  task | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 |  duplicate
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by weasel):

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


Comment:

 Apparently already created that account with #23569 months ago.

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

Re: [tor-bugs] #24997 [Internal Services/Tor Sysadmin Team]: please add boklm to torextratpo group

2018-01-24 Thread Tor Bug Tracker & Wiki
#24997: please add boklm to torextratpo group
-+
 Reporter:  arma |  Owner:  tpa
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+
Changes (by weasel):

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


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

Re: [tor-bugs] #22659 [Applications/Tor Browser]: Changes to `intl.accept.languages` get overwritten after restart

2018-01-24 Thread Tor Bug Tracker & Wiki
#22659: Changes to `intl.accept.languages` get overwritten after restart
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-7.0-issues, tbb-regression,  |  Actual Points:
  GeorgKoppen201801, TorBrowserTeam201801|
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by gk):

 * cc: mcs, brade (added)


Comment:

 An update on that one: It seems there are different issues here at work.
 The one is that the `intl.accept_languages` pref is not correctly
 updated/shown and the other one is that the wrong header values are sent.

 Surprisingly, those issues don't belong together. I.e. the first one is
 fixed with Tor Browser 7.5a8, more exactly with the TorLauncher 0.2.14.1
 update. The other one is unaffected by it.
 https://bugzilla.mozilla.org/show_bug.cgi?id=1005640 fixed a pretty
 similar problem for Firefox (it landed in version 55). I guess a next step
 would be to backport that patch and look whether we are good on ESR 52 as
 well.

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

Re: [tor-bugs] #24857 [Core Tor/Tor]: tor 0.3.1.9 100% cpu load

2018-01-24 Thread Tor Bug Tracker & Wiki
#24857: tor 0.3.1.9 100% cpu load
--+---
 Reporter:  Eugene646 |  Owner:  (none)
 Type:  defect| Status:  needs_information
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:  Tor: 0.3.1.9
 Severity:  Normal| Resolution:
 Keywords:  cpu, windows  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---

Comment (by creideiki):

 I restarted the Tor service and watched it closely. The error message
 "Failing because we have 4063 connections already" appears at the same
 time as it starts using 100% CPU. This time it took 6 minutes.

 At 3 minutes after starting the service, well after the log says the relay
 is up and running, "perf top" looks nice and sane like this:
 {{{
 16.76%  tor [.] curve25519_donna
  3.18%  libcrypto.so.1.0.0  [.] __bn_sqrx8x_reduction
  1.93%  libcrypto.so.1.0.0  [.] mulx4x_internal
  1.79%  libcrypto.so.1.0.0  [.] bn_sqrx8x_internal
  1.62%  tor [.] connection_bucket_refill
  1.58%  tor [.] tor_memcmp
  1.40%  libc-2.26.so[.] _int_malloc
  1.37%  libc-2.26.so[.] malloc
  1.29%  libcrypto.so.1.0.0  [.] sha256_block_data_order_avx2
  0.99%  libc-2.26.so[.] __memmove_avx_unaligned_erms
  0.96%  libc-2.26.so[.] _int_free
  0.93%  tor [.] tor_memeq
  0.73%  tor [.] buf_datalen
  0.73%  [kernel][k] ___bpf_prog_run
  0.71%  [kernel][k] syscall_return_via_sysret
  0.61%  libcrypto.so.1.0.0  [.] __ecp_nistz256_mul_montx
  0.57%  [kernel][k] __fget
  0.55%  libcrypto.so.1.0.0  [.] __ecp_nistz256_sqr_montx
  0.53%  libcrypto.so.1.0.0  [.] sha1_block_data_order_avx2
  0.52%  tor [.] channel_update_bad_for_new_circs
  0.46%  libssl.so.1.0.0 [.] ssl_cipher_apply_rule.isra.1
  0.45%  libpthread-2.26.so  [.] __pthread_mutex_lock
  0.43%  libc-2.26.so[.] cfree@GLIBC_2.2.5
  0.42%  libcrypto.so.1.0.0  [.] _aesni_ctr32_ghash_6x
 }}}
 After 6 minutes, when the error message has appeared in the log and the
 process uses 100% CPU, "perf top" looks like this:
 {{{
  9.45%  [kernel]   [k] syscall_return_via_sysret
  6.33%  [unknown]  [k] 0xfe0b601e
  5.16%  [kernel]   [k] ep_send_events_proc
  3.48%  [kernel]   [k] ___bpf_prog_run
  3.38%  [kernel]   [k] _raw_spin_lock_irqsave
  3.19%  [kernel]   [k] read_tsc
  3.06%  [kernel]   [k] __fget
  2.75%  libpthread-2.26.so [.] __pthread_mutex_lock
  2.55%  [kernel]   [k] _raw_spin_unlock_irqrestore
  2.49%  [kernel]   [k] seccomp_run_filters
  2.33%  libc-2.26.so   [.] epoll_pwait
  2.27%  [kernel]   [k] select_estimate_accuracy
  2.25%  libpthread-2.26.so [.] __pthread_mutex_unlock_usercnt
  1.84%  [kernel]   [k] syscall_trace_enter
  1.81%  [kernel]   [k] __seccomp_filter
  1.78%  libevent-2.1.so.6.0.2  [.] event_base_loop
  1.65%  [kernel]   [k] ep_scan_ready_list.constprop.15
  1.57%  [unknown]  [k] 0xfe00601e
  1.52%  [kernel]   [k] ep_poll
  1.41%  [kernel]   [k] ktime_get_ts64
  1.36%  [kernel]   [k] entry_SYSCALL_64_after_hwframe
  1.35%  libevent-2.1.so.6.0.2  [.] event_callback_activate_nolock_
  1.29%  [unknown]  [k] 0xfe0b6000
  1.10%  tor[.] assert_connection_ok
 }}}
 And says the Tor process is spending 65% of its time in the kernel.
 Probably with those 69k/s epoll_pwait() calls.

 Network statistics says it's still shuffling its 10Mb/s, though, so it's
 doing something productive as well.

 Final Tor log is not very interesting, but for completeness:
 {{{
 Jan 24 10:49:47.000 [notice] Tor 0.3.2.9 (git-9e8b762fcecfece6) opening
 log file.
 Jan 24 10:49:47.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.
 Jan 24 10:49:48.000 [notice] Parsing GEOIP IPv6 file
 /usr/share/tor/geoip6.
 Jan 24 10:49:48.000 [notice] Configured to measure statistics. Look for
 the *-stats files that will first be written to the data directory in 24
 hours from now.
 Jan 24 10:49:48.000 [notice] Your Tor server's identity key fingerprint is
 CENSORED
 Jan 24 10:49:48.000 [notice] Bootstrapped 0%: Starting
 Jan 24 10:49:54.000 [notice] Starting with guard context "default"
 Jan 24 10:49:54.000 [notice] Bootstrapped 80%: Connecting to the Tor
 network
 Jan 24 10:49:54.000 [notice] Self-testing indicates your ORPort is
 reachable from the outside. Excellent.
 Jan 24 10:49:54.000 [notice] 

Re: [tor-bugs] #24857 [Core Tor/Tor]: tor 0.3.1.9 100% cpu load

2018-01-24 Thread Tor Bug Tracker & Wiki
#24857: tor 0.3.1.9 100% cpu load
--+---
 Reporter:  Eugene646 |  Owner:  (none)
 Type:  defect| Status:  needs_information
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:  Tor: 0.3.1.9
 Severity:  Normal| Resolution:
 Keywords:  cpu, windows  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---

Comment (by creideiki):

 I think I'm seeing this same bug, or at least something very similar.

 I run Tor as a non-exit relay in an LXC container on a Gentoo Linux box on
 an Intel Core i7-6700K, with Tor constantly shuffling 10Mb/s of traffic.
 Some random time after starting the Tor service, it starts eating one
 entire CPU core.

 I'm not sure if it's related, since I don't have CPU usage history for
 this container and thus don't know when the 100% CPU usage started, but
 the Tor log contains a lot of these messages:

Jan 24 05:17:24.000 [warn] Failing because we have 4063 connections
 already. Please read doc/TUNING for guidance. [over 1601 similar
 message(s) suppressed in last 21600 seconds]

 If that suppression count is correct, that's 740 messages per second,
 which seems a bit excessive.

 I'm currently running this package:

net-vpn/tor-0.3.2.9::gentoo was built with the following:
USE="-libressl -lzma -scrypt seccomp (-selinux) -systemd -test tor-
 hardening -web -zstd" ABI_X86="(64)"

 The logs suggest the following timeline:

 Dec 9: First occurrence of the "Failing because we have X connections
 already" message, X=29967, on a Tor 0.3.2.2-alpha with 55 days of uptime.
 Dec 10: Next message, X=29967.
 Dec 15: Tor upgraded to 0.3.2.6-alpha.
 Dec 22: Next message, X=29967, at 6 days 6 hours uptime.
 Dec 30: Next message, X=29967, at 15 days 6 hours uptime.
 Jan 1: 2 messages, X=29967, with 6 hours interval.
 Jan 2: 1 message, X=29967, 21 hours after the last one.
 Jan 7: Machine is rebooted to kernel 4.14.11 to get initial Meltdown
 patches. Failure messages start coming 4 minutes after starting the
 service, with X=4063.
 Jan 7-21: Failure messages come regularly every 6 hours, X=4063.
 Jan 21: Tor is upgraded to 0.3.2.9. Failure messages start coming 7
 minutes after starting the service, with X=4063.
 Jan 21-24 (now): Failure messages come regularly every 6 hours, X=4063.

 The Tor process uses 100% CPU (i.e. one core), but not very much memory -
 currently 900M virtual, 300M resident.

 "perf top" on the Tor process isn't very helpful; at the top is perf's own
 BPF stuff at 5-10% CPU time, followed by pthread functions in glibc at
 ~2-3%. Actual Tor code is way down the list; the only function visible
 without going ridiculously low is "assert_connection_ok" at 1% CPU time.

 "strace" on the Tor process sees mostly calls to epoll_pwait():

[pid 23279] 1516784382.485502 epoll_pwait(3, [{EPOLLIN, {u32=9,
 u64=9}}], 512, 9, NULL, 8) = 1

 Actually, a whole lot of them; strace counts around 69000 such calls per
 second, with other syscalls during one random second coming in at much
 lower counts:

   1 accept4
   1 close
   1 setsockopt
 174 getpid
 311 futex
 682 write
 967 getsockopt
 967 ioctl
1116 epoll_ctl
1561 read

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

Re: [tor-bugs] #24998 [Applications/Tor Browser]: A user may of found a DNS leak in OnionBrowser 2

2018-01-24 Thread Tor Bug Tracker & Wiki
#24998: A user may of found a DNS leak in OnionBrowser 2
--+--
 Reporter:  Dbryrtfbcbhgf |  Owner:  tbb-team
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:  invalid
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by Dbryrtfbcbhgf):

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


Comment:

 Dev responded

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

Re: [tor-bugs] #24998 [Applications/Tor Browser]: A user may of found a DNS leak in OnionBrowser 2

2018-01-24 Thread Tor Bug Tracker & Wiki
#24998: A user may of found a DNS leak in OnionBrowser 2
--+--
 Reporter:  Dbryrtfbcbhgf |  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 Dbryrtfbcbhgf):

 * owner:  (none) => tbb-team
 * component:  Applications => Applications/Tor Browser


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

[tor-bugs] #24998 [Applications]: A user may of found a DNS leak in OnionBrowser 2

2018-01-24 Thread Tor Bug Tracker & Wiki
#24998: A user may of found a DNS leak in OnionBrowser 2
---+
 Reporter:  Dbryrtfbcbhgf  |  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Applications   |Version:
 Severity:  Normal |   Keywords:
Actual Points: |  Parent ID:
   Points: |   Reviewer:
  Sponsor: |
---+
 A user may of found a DNS leak in OnionBrowser 2, what should he do.
 https://github.com/mtigas/OnionBrowser/issues/112

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

Re: [tor-bugs] #24994 [Webpages/Website]: Replace tor-experimental-0.3.0.x with tor-nightly-master on the debian page

2018-01-24 Thread Tor Bug Tracker & Wiki
#24994: Replace tor-experimental-0.3.0.x with tor-nightly-master on the debian 
page
--+
 Reporter:  teor  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by cypherpunks):

 I tried to get "alpha" or "testing" named repos 3 years ago but weasel
 does not like that
 https://lists.torproject.org/pipermail/tor-dev/2015-March/008582.html

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

Re: [tor-bugs] #24994 [Webpages/Website]: Replace tor-experimental-0.3.0.x with tor-nightly-master on the debian page

2018-01-24 Thread Tor Bug Tracker & Wiki
#24994: Replace tor-experimental-0.3.0.x with tor-nightly-master on the debian 
page
--+
 Reporter:  teor  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by teor):

 Replying to [comment:1 cypherpunks]:
 > Replying to [ticket:24994 teor]:
 > > We tell people to use the Tor 0.3.0 packages for the development
 branch:
 >
 > For thouse that are unable to find "0.3.0" either "view source" or
 disable JavaScript in your browser.
 >
 > > But Tor 0.3.0 will not be supported on 1 February 2018.
 > >
 > > To avoid changing this every 6 months, let's use tor-nightly-master-
 DISTRIBUTION instead.
 >
 > Do you want this change only for the  version of the page or
 the entire page?
 > Switching to "experimantal" instructions to MASTER will reduce the
 amount of testing alpha releases will get.

 You're right.

 We are just starting a new alpha series in the next week or two.
 Let's get builders going for 0.3.3, then change both versions of the page
 to point to 0.3.3.
 It would be even nicer if we just had a master, alpha, and stable branch.
 That's a conversation we had on tor-dev. I'll bump it again.

 Can we also link full list of available releases from both the noscript
 and script versions of the page?
 http://deb.torproject.org/torproject.org/dists/

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

Re: [tor-bugs] #24995 [Applications/Tor Browser]: Truncated git hash not available in the windows expert bundle build for Tor 0.3.2.9

2018-01-24 Thread Tor Bug Tracker & Wiki
#24995: Truncated git hash not available in the windows expert bundle build for 
Tor
0.3.2.9
--+--
 Reporter:  TheDcoder |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:  Tor: 0.3.2.9
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by boklm):

 Ah yes, it is probably because with `rbm/tor-browser-build` the .git
 directory is not available anymore when we do the build.

 I think we could fix that by adding the hash in the file `micro-
 revision.i` during the build.

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

Re: [tor-bugs] #23650 [Core Tor/Tor]: Tor source code has many typos

2018-01-24 Thread Tor Bug Tracker & Wiki
#23650: Tor source code has many typos
--+--
 Reporter:  cypherpunks   |  Owner:  arma
 Type:  defect| Status:  new
 Priority:  Very Low  |  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:
 Severity:  Trivial   | Resolution:
 Keywords:  easy  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by fristonio):

 I am ready with my patch, what is the preferred way to submit the patch,
 should I upload it to github on a gist or in a repository in my github
 profile or should I upload it here only?

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

Re: [tor-bugs] #24994 [Webpages/Website]: Replace tor-experimental-0.3.0.x with tor-nightly-master on the debian page

2018-01-24 Thread Tor Bug Tracker & Wiki
#24994: Replace tor-experimental-0.3.0.x with tor-nightly-master on the debian 
page
--+
 Reporter:  teor  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by cypherpunks):

 Found the content, that URL should be replaced with:
 https://www.torproject.org/download/download-unix.html.en#packagediff

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

Re: [tor-bugs] #24994 [Webpages/Website]: Replace tor-experimental-0.3.0.x with tor-nightly-master on the debian page

2018-01-24 Thread Tor Bug Tracker & Wiki
#24994: Replace tor-experimental-0.3.0.x with tor-nightly-master on the debian 
page
--+
 Reporter:  teor  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by cypherpunks):

 also: the url pointing to
 https://www.torproject.org/download/download.html.en#packagediff
 is not valid (this anchor does no longer exist)

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

Re: [tor-bugs] #23650 [Core Tor/Tor]: Tor source code has many typos

2018-01-24 Thread Tor Bug Tracker & Wiki
#23650: Tor source code has many typos
--+--
 Reporter:  cypherpunks   |  Owner:  arma
 Type:  defect| Status:  new
 Priority:  Very Low  |  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:
 Severity:  Trivial   | Resolution:
 Keywords:  easy  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by fristonio):

 There was an error in tests due to the correction of this spelling
 https://gitweb.torproject.org/tor.git/tree/src/test/test_microdesc.c#n574
 . I guess there might be some comparison with the key string due to which
 test failed on changing the spelling so I am letting this one to persist
 if its ok.

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

Re: [tor-bugs] #24994 [Webpages/Website]: Replace tor-experimental-0.3.0.x with tor-nightly-master on the debian page

2018-01-24 Thread Tor Bug Tracker & Wiki
#24994: Replace tor-experimental-0.3.0.x with tor-nightly-master on the debian 
page
--+
 Reporter:  teor  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by cypherpunks):

 Replying to [ticket:24994 teor]:
 > We tell people to use the Tor 0.3.0 packages for the development branch:

 For thouse that are unable to find "0.3.0" either "view source" or disable
 JavaScript in your browser.

 > But Tor 0.3.0 will not be supported on 1 February 2018.
 >
 > To avoid changing this every 6 months, let's use tor-nightly-master-
 DISTRIBUTION instead.

 Do you want this change only for the  version of the page or the
 entire page?
 Switching to "experimantal" instructions to MASTER will reduce the amount
 of testing alpha releases will get.

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

<    1   2