Re: [tor-bugs] #33651 [Core Tor/Tor]: Suspicious "fetched this many bytes" counts from #32720

2020-03-25 Thread Tor Bug Tracker & Wiki 
#33651: Suspicious "fetched this many bytes" counts from #32720
--+
 Reporter:  arma  |  Owner:  nickm
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:  Tor: 0.4.4.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:|  Actual Points:  0
Parent ID:| Points:
 Reviewer:  dgoulet   |Sponsor:
--+
Changes (by nickm):

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


Comment:

 Merged to master. No changes entry, since the bug has not been in any
 stable release.

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

Re: [tor-bugs] #33651 [Core Tor/Tor]: Suspicious "fetched this many bytes" counts from #32720

2020-03-23 Thread Tor Bug Tracker & Wiki 
#33651: Suspicious "fetched this many bytes" counts from #32720
--+
 Reporter:  arma  |  Owner:  nickm
 Type:  defect| Status:  merge_ready
 Priority:  Medium|  Milestone:  Tor: 0.4.4.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:  0
Parent ID:| Points:
 Reviewer:  dgoulet   |Sponsor:
--+

Comment (by nickm):

 That appveyor failure is #33643

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

Re: [tor-bugs] #33651 [Core Tor/Tor]: Suspicious "fetched this many bytes" counts from #32720

2020-03-23 Thread Tor Bug Tracker & Wiki 
#33651: Suspicious "fetched this many bytes" counts from #32720
--+
 Reporter:  arma  |  Owner:  nickm
 Type:  defect| Status:  merge_ready
 Priority:  Medium|  Milestone:  Tor: 0.4.4.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:  0
Parent ID:| Points:
 Reviewer:  dgoulet   |Sponsor:
--+
Changes (by dgoulet):

 * status:  needs_review => merge_ready
 * reviewer:   => dgoulet


Comment:

 For some reasons, one of Appveyor builds failed with:

 
https://ci.appveyor.com/project/torproject/tor/builds/31574905/job/7nyl60kltec1gs4h

 {{{
   FAIL ../src/test/test_crypto.c:237: OpenSSL library version 1.1.1d did
 not begin with header version 1.1.1e.
 }}}

 Seems unrelated so apart from that, lgtm. Feel free to merge.

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

Re: [tor-bugs] #33651 [Core Tor/Tor]: Suspicious "fetched this many bytes" counts from #32720

2020-03-20 Thread Tor Bug Tracker & Wiki 
#33651: Suspicious "fetched this many bytes" counts from #32720
--+
 Reporter:  arma  |  Owner:  nickm
 Type:  defect| Status:  needs_review
 Priority:  Medium|  Milestone:  Tor: 0.4.4.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:  0
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by arma):

 Looking promising!
 {{{
 Mar 20 05:59:37.013 [notice] Heartbeat: Tor's uptime is 3:31 hours, with
 14 circuits open. I've sent 366 kB and received 1.20 MB.
 Mar 20 05:59:37.014 [notice] While bootstrapping, fetched this many bytes:
 Mar 20 05:59:37.014 [notice] 394532 (microdescriptor fetch)
 Mar 20 05:59:37.014 [notice] While not bootstrapping, fetched this many
 bytes:
 Mar 20 05:59:37.014 [notice] 212736 (consensus network-status fetch)
 Mar 20 05:59:37.014 [notice] 5935 (hidden-service v2 descriptor fetch)
 Mar 20 05:59:37.014 [notice] 55871 (microdescriptor fetch)
 }}}

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

Re: [tor-bugs] #33651 [Core Tor/Tor]: Suspicious "fetched this many bytes" counts from #32720

2020-03-19 Thread Tor Bug Tracker & Wiki 
#33651: Suspicious "fetched this many bytes" counts from #32720
--+
 Reporter:  arma  |  Owner:  nickm
 Type:  defect| Status:  needs_review
 Priority:  Medium|  Milestone:  Tor: 0.4.4.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:  0
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by nickm):

 (If there are two commits in this PR, then it's safe to ignore the first
 one: It's already been merged to master.)

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

Re: [tor-bugs] #33651 [Core Tor/Tor]: Suspicious "fetched this many bytes" counts from #32720

2020-03-19 Thread Tor Bug Tracker & Wiki 
#33651: Suspicious "fetched this many bytes" counts from #32720
--+
 Reporter:  arma  |  Owner:  nickm
 Type:  defect| Status:  needs_review
 Priority:  Medium|  Milestone:  Tor: 0.4.4.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:  0
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by nickm):

 * status:  accepted => needs_review
 * actualpoints:   => 0


Comment:

 okay, this looks like a simple mistake. Fix is in `bug33651` with PR at
 https://github.com/torproject/tor/pull/1810

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

Re: [tor-bugs] #33651 [Core Tor/Tor]: Suspicious "fetched this many bytes" counts from #32720

2020-03-19 Thread Tor Bug Tracker & Wiki 
#33651: Suspicious "fetched this many bytes" counts from #32720
--+
 Reporter:  arma  |  Owner:  nickm
 Type:  defect| Status:  accepted
 Priority:  Medium|  Milestone:  Tor: 0.4.4.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by nickm):

 * status:  new => accepted
 * owner:  (none) => nickm
 * milestone:   => Tor: 0.4.4.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] #33651 [Core Tor/Tor]: Suspicious "fetched this many bytes" counts from #32720

2020-03-18 Thread Tor Bug Tracker & Wiki 
#33651: Suspicious "fetched this many bytes" counts from #32720
--+
 Reporter:  arma  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by arma):

 I should clarify that I'm running with safelogging 0.

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

[tor-bugs] #33651 [Core Tor/Tor]: Suspicious "fetched this many bytes" counts from #32720

2020-03-18 Thread Tor Bug Tracker & Wiki 
#33651: Suspicious "fetched this many bytes" counts from #32720
--+
 Reporter:  arma  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 Following #32720, now I have these log messages in my Tor client:
 {{{
 Mar 17 17:52:52.004 [notice] Bootstrapped 100% (done): Done
 Mar 17 23:52:49.170 [notice] Heartbeat: Tor's uptime is 6:00 hours, with 0
 circuits open. I've sent 166.22 MB and received 5.25 GB.
 Mar 17 23:52:49.178 [notice] While bootstrapping, fetched this many bytes:
 Mar 17 23:52:49.178 [notice] 542559 (consensus network-status fetch)
 Mar 17 23:52:49.178 [notice] While not bootstrapping, fetched this many
 bytes:
 Mar 17 23:52:49.178 [notice] 542559 (consensus network-status fetch)
 Mar 17 23:52:49.178 [notice] Average packaged cell fullness: 52.843%. TLS
 write overhead: 3%
 Mar 18 17:01:52.177 [notice] Your system clock just jumped 44387 seconds
 forward; assuming established circuits no longer work.
 Mar 18 18:12:33.010 [notice] Heartbeat: Tor's uptime is 11:59 hours, with
 0 circuits open. I've sent 166.25 MB and received 5.25 GB.
 Mar 18 18:12:33.011 [notice] While bootstrapping, fetched this many bytes:
 Mar 18 18:12:33.011 [notice] 542559 (consensus network-status fetch)
 Mar 18 18:12:33.011 [notice] While not bootstrapping, fetched this many
 bytes:
 Mar 18 18:12:33.011 [notice] 542559 (consensus network-status fetch)
 Mar 18 18:12:33.011 [notice] Average packaged cell fullness: 52.898%. TLS
 write overhead: 3%
 Mar 19 00:12:33.013 [notice] Heartbeat: Tor's uptime is 17:59 hours, with
 0 circuits open. I've sent 166.26 MB and received 5.25 GB.
 Mar 19 00:12:33.013 [notice] While bootstrapping, fetched this many bytes:
 Mar 19 00:12:33.013 [notice] 542559 (consensus network-status fetch)
 Mar 19 00:12:33.013 [notice] While not bootstrapping, fetched this many
 bytes:
 Mar 19 00:12:33.013 [notice] 542559 (consensus network-status fetch)
 Mar 19 00:12:33.013 [notice] Average packaged cell fullness: 52.953%. TLS
 write overhead: 3%
 }}}

 I'm running
 {{{
 Tor 0.4.4.0-alpha-dev (git-d4595b344a1a3254) running on Linux with
 Libevent 2.1.8-stable, OpenSSL 1.1.1d, Zlib 1.2.11, Liblzma 5.2.4, and
 Libzstd N/A.
 }}}

 It is surprising to me that I have the same number while bootstrapping and
 while not bootstrapping, and that number doesn't seem to go up.

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