Re: [tor-bugs] #28614 [Core Tor/Tor]: Can't parse networkstatus consensus time

[Tor Bug Tracker & Wiki]

#28614: Can't parse networkstatus consensus time
--+
 Reporter:  Vort  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.4.0.x-final
Component:  Core Tor/Tor  |Version:  Tor: 0.3.5.5-alpha
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by Vort):

 Never seen this with 0.3.4.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] #27967 [Core Tor/Chutney]: Ignore the Linux sandbox warning in chutney

[Tor Bug Tracker & Wiki]

#27967: Ignore the Linux sandbox warning in chutney
--+
 Reporter:  teor  |  Owner:  teor
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Core Tor/Chutney  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by teor):

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


Comment:

 Merged to master as commit 7387258.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #27969 [Core Tor/Chutney]: Rename some confusing torrc_templates

[Tor Bug Tracker & Wiki]

#27969: Rename some confusing torrc_templates
--+
 Reporter:  teor  |  Owner:  teor
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Core Tor/Chutney  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by teor):

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


Comment:

 We don't have a full CI infrastructure yet, but this change passes `make
 test-network-all` on tor-0.3.5.

 Merged to chutney master as 6c45e79.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #28247 [Core Tor/Tor]: Use build.rs in place of test_linking_hack

[Tor Bug Tracker & Wiki]

#28247: Use build.rs in place of test_linking_hack
--+
 Reporter:  nickm |  Owner:  nickm
 Type:  defect| Status:  needs_revision
 Priority:  Medium|  Milestone:  Tor: 0.3.5.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  035-can   |  Actual Points:  .1
Parent ID:  #28244| Points:  .1
 Reviewer:  catalyst  |Sponsor:
--+
Changes (by catalyst):

 * status:  needs_review => needs_revision


Comment:

 The pull request seems to fail Travis, but only in the Rust builds. Maybe
 something is missing? It seems related to the Rust linker somehow? I
 haven't investigated further yet.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #28382 [Core Tor/Tor]: Update bandwidth file headers in dir-spec

[Tor Bug Tracker & Wiki]

#28382: Update bandwidth file headers in dir-spec
--+
 Reporter:  juga  |  Owner:  juga
 Type:  task  | Status:  merge_ready
 Priority:  Medium|  Milestone:  Tor: 0.4.0.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tor-spec  |  Actual Points:
Parent ID:| Points:
 Reviewer:  teor  |Sponsor:
--+
Changes (by teor):

 * reviewer:  mikeperry, teor => teor


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #28382 [Core Tor/Tor]: Update bandwidth file headers in dir-spec

[Tor Bug Tracker & Wiki]

#28382: Update bandwidth file headers in dir-spec
-+
 Reporter:  juga |  Owner:  juga
 Type:  task | Status:  merge_ready
 Priority:  Medium   |  Milestone:  Tor: 0.4.0.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-spec |  Actual Points:
Parent ID:   | Points:
 Reviewer:  mikeperry, teor  |Sponsor:
-+
Changes (by teor):

 * status:  needs_review => merge_ready


Comment:

 It's been 2 weeks, so I'm going to review this ticket.

 This is a trivial deletion that looks good to me.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #23588 [Core Tor/Tor]: Write fascist_firewall_choose_address_ls() and use it in hs_get_extend_info_from_lspecs()

[Tor Bug Tracker & Wiki]

#23588: Write fascist_firewall_choose_address_ls() and use it in
hs_get_extend_info_from_lspecs()
-+-
 Reporter:  teor |  Owner:  neel
 Type:  enhancement  | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.0.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  prop224, tor-hs, single-onion,   |  Actual Points:
  ipv6, 034-triage-20180328, |
  034-removed-20180328   |
Parent ID:  #23493   | Points:  1
 Reviewer:  teor |Sponsor:
-+-
Changes (by teor):

 * status:  needs_review => needs_revision


Comment:

 We all get busy at times.

 Thanks for these tests.
 It looks like we're missing a few tests for each function.

 I commented on the pull request.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #28229 [Core Tor/Tor]: Possible race condition opening SOCKS Port in test_rebind.py

[Tor Bug Tracker & Wiki]

#28229: Possible race condition opening SOCKS Port in test_rebind.py
-+
 Reporter:  teor |  Owner:  rl1987
 Type:  defect   | Status:  merge_ready
 Priority:  High |  Milestone:  Tor: 0.3.5.x-final
Component:  Core Tor/Tor |Version:  Tor: 0.3.5.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  tor-ci, 035-can  |  Actual Points:
Parent ID:   | Points:
 Reviewer:  teor |Sponsor:
-+
Changes (by teor):

 * status:  needs_review => merge_ready


Comment:

 This change seems fine to me.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #28596 [Core Tor/sbws]: Use the latest descriptor bandwidths for torflow weighting

[Tor Bug Tracker & Wiki]

#28596: Use the latest descriptor bandwidths for torflow weighting
---+-
 Reporter:  teor   |  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:  sbws 1.0 (MVP must)
Component:  Core Tor/sbws  |Version:  sbws: 1.0.0
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID:  #28588 | Points:
 Reviewer: |Sponsor:
---+-

Comment (by teor):

 Replying to [comment:1 juga]:
 > Looking more torflow's code, now i'm not sure:
 https://gitweb.torproject.org/pytorctl.git/tree/SQLSupport.py#n421,
 https://gitweb.torproject.org/pytorctl.git/tree/SQLSupport.py#n691.

 This SQLSupport code is not executed by the torflow BwAuthority.

 The torflow BwAuthority generates bandwidth files using the aggregate.py
 script:
 
https://gitweb.torproject.org/torflow.git/tree/NetworkScanners/BwAuthority/aggregate.py#n884

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #28602 [Core Tor/sbws]: The call to generate the bw file is passing an old argument

[Tor Bug Tracker & Wiki]

#28602: The call to generate the bw file is passing an old argument
---+-
 Reporter:  juga   |  Owner:  juga
 Type:  defect | Status:  needs_revision
 Priority:  Medium |  Milestone:  sbws 1.0 (MVP must)
Component:  Core Tor/sbws  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID:  #25925 | Points:
 Reviewer: |Sponsor:
---+-
Changes (by teor):

 * status:  needs_review => needs_revision


Comment:

 Removing a command-line argument is a breaking change.

 Please keep the old argument for compatibility.
 (Or increment the sbws version to 2.0.)

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

Re: [tor-bugs] #28547 [Core Tor/sbws]: Monitor relays that are not measured by each sbws instance

[Tor Bug Tracker & Wiki]

#28547: Monitor relays that are not measured by each sbws instance
---+-
 Reporter:  teor   |  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:  sbws 1.0 (MVP must)
Component:  Core Tor/sbws  |Version:
 Severity:  Normal | Resolution:
 Keywords:  tor-bwauth |  Actual Points:
Parent ID:  #25925 | Points:
 Reviewer: |Sponsor:
---+-

Comment (by teor):

 Replying to [comment:4 juga]:
 > The KeyValues that depend on the scanner (not the generator), would be
 only written once a day, so we would need to look at the bandwidth files
 generated at 00:35 UTC. Any potential problem with that?.

 Why can't we report those values every hour, for the last hour?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #28600 [Core Tor/sbws]: Refactor: store the minimum of the bandwidth values from the consenus in the results

[Tor Bug Tracker & Wiki]

#28600: Refactor: store the minimum of the bandwidth values from the consenus in
the results
---+
 Reporter:  juga   |  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Core Tor/sbws  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID:  #25925 | Points:
 Reviewer: |Sponsor:
---+

Comment (by teor):

 Replying to [ticket:28600 juga]:
 > Currently we store the descriptor and network status bandwidth values in
 the raw results to be able to calculate the minimum from them in the
 bandwidth file.
 > In case we don't need to these values for anything else, we could
 calculate and store the minimum of them in the bandwidth raw results.

 The bug #28588 happened because torflow did a calculation and stored one
 value.
 We can avoid future bugs like #28588 by taking the minimum as late as
 possible.

 I think we should not do this refactor.
 What do you think?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #28588 [Core Tor/sbws]: SBWS 'bw_torflow_scale' does not appear to honor relay MaxAdvertisedBandwidth

[Tor Bug Tracker & Wiki]

#28588: SBWS 'bw_torflow_scale' does not appear to honor relay
MaxAdvertisedBandwidth
---+-
 Reporter:  starlight  |  Owner:  (none)
 Type:  defect | Status:  needs_review
 Priority:  Medium |  Milestone:  sbws 1.0 (MVP must)
Component:  Core Tor/sbws  |Version:  sbws: 1.0.0
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+-
Changes (by teor):

 * status:  new => needs_review


Comment:

 Replying to [comment:9 juga]:
 > I've the branch
 https://github.com/torproject/sbws/compare/master...juga0:bug28588

 Setting this ticket to needs_review.
 Let's ask at the meeting if anyone wants to review it.

 > but now i wonder whether i should solve #28600, or just leave it for
 some future refactoring.

 I will comment on that ticket.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #12381 [Obfuscation/Obfsproxy]: Pluggable Transports + proxy is not working on Windows with Tor Browser

[Tor Bug Tracker & Wiki]

#12381: Pluggable Transports + proxy is not working on Windows with Tor Browser
---+--
 Reporter:  gk |  Owner:  asn
 Type:  defect | Status:  reopened
 Priority:  High   |  Milestone:
Component:  Obfuscation/Obfsproxy  |Version:
 Severity:  Normal | Resolution:
 Keywords:  tbb-helpdesk-frequent  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--

Comment (by kpdyer):

 I think phasing out fteproxy and moving to Marionette is a good idea
 because fteproxy is essentially unsupported/unfunded.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #28521 [Obfuscation/FTE]: fte is not working using default tor browser bridges

[Tor Bug Tracker & Wiki]

#28521: fte is not working using default tor browser bridges
-+---
 Reporter:  boklm|  Owner:  kpdyer
 Type:  defect   | Status:  needs_information
 Priority:  Medium   |  Milestone:
Component:  Obfuscation/FTE  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+---

Comment (by kpdyer):

 Yep, I'm the owner for these.

  - 128.105.214.161 had a hardware failure and is permanently offline.
  - 128.105.214.162/128.105.214.163 are experiencing some sort of transient
 failure but I'm not physically located near these machines. I've asked
 someone to look into it and I should have an answer soon.
  - 131.252.210.150 was in a bad state but I was able to resolve it. Can
 you confirm it's workin for you 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] #28617 [Applications/Tor Browser]: Tor Browser failed to start on Windows 10 when Dvorak Programmer layout is used

[Tor Bug Tracker & Wiki]

#28617: Tor Browser failed to start on Windows 10 when Dvorak Programmer layout 
is
used
--+--
 Reporter:  vp1981|  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 arma):

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


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

Re: [tor-bugs] #28613 [Core Tor/Tor]: Log is filled with OpenSSL errors

[Tor Bug Tracker & Wiki]

#28613: Log is filled with OpenSSL errors
--+
 Reporter:  Vort  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.4.0.x-final
Component:  Core Tor/Tor  |Version:  Tor: 0.3.5.5-alpha
 Severity:  Normal| Resolution:
 Keywords:  ssl 035-backport  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by arma):

 See #28616 for a very related issue but on linux

 Is the issue openssl 1.1.1a?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #28616 [Core Tor/Tor]: TLS internal error running Tor 0.3.4.9 on Debian Buster (OpenSSL 1.1.1a)

[Tor Bug Tracker & Wiki]

#28616: TLS internal error running Tor 0.3.4.9 on Debian Buster (OpenSSL 1.1.1a)
--+--
 Reporter:  filippo   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:  Tor: 0.3.4.9
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by arma):

 See #28613 for a very related issue but on windows

 Is the issue openssl 1.1.1a?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #26690 [Applications/Tor Browser]: TBA: Port padlock states for .onion services to mobile

[Tor Bug Tracker & Wiki]

#26690: TBA: Port padlock states for .onion services to mobile
-+-
 Reporter:  igt0 |  Owner:  tbb-
 |  team
 Type:  enhancement  | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-mobile, TBA-a2,  |  Actual Points:
  TorBrowserTeam201811   |
Parent ID:  #5709| Points:
 Reviewer:   |Sponsor:
 |  Sponsor8
-+-
Changes (by igt0):

 * status:  needs_revision => needs_review


Comment:

 I updated the commit msg and the indentation:

 https://trac.torproject.org/projects/tor/attachment/ticket/26690/0001-Bug-26690
 -Port-padlock-states-for-.onion-services-to.3.patch

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #26690 [Applications/Tor Browser]: TBA: Port padlock states for .onion services to mobile

[Tor Bug Tracker & Wiki]

#26690: TBA: Port padlock states for .onion services to mobile
-+-
 Reporter:  igt0 |  Owner:  tbb-
 |  team
 Type:  enhancement  | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-mobile, TBA-a2,  |  Actual Points:
  TorBrowserTeam201811   |
Parent ID:  #5709| Points:
 Reviewer:   |Sponsor:
 |  Sponsor8
-+-
Changes (by igt0):

 * Attachment "0001-Bug-26690-Port-padlock-states-for-.onion-services-
 to.3.patch" 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] #28617 [- Select a component]: Tor Browser failed to start on Windows 10 when Dvorak Programmer layout is used

[Tor Bug Tracker & Wiki]

#28617: Tor Browser failed to start on Windows 10 when Dvorak Programmer layout 
is
used
+--
 Reporter:  vp1981  |  Owner:  (none)
 Type:  defect  | Status:  new
 Priority:  Medium  |  Component:  - Select a component
  Version:  |   Severity:  Normal
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
 Hello,

 from time to time tor browser failed to start on Windows 10 when drovar
 programmer keyboard layout is installed. This is from Event viewer:

 {{{
 Faulting application name: firefox.exe, version: 60.3.0.6609, time stamp:
 0x
 Faulting module name: kbddvp.dll, version: 1.2.7.0, time stamp: 0x54cec1e7
 Exception code: 0xc005
 Fault offset: 0x25d8
 Faulting process id: 0x5428
 Faulting application start time: 0x01d48522c5608cc1
 Faulting application path: D:\Users\%USERNAME%\programs\tor-
 browser\Browser\firefox.exe
 Faulting module path: C:\WINDOWS\SYSTEM32\kbddvp.dll
 Report Id: 093954cb-3a3a-4f4c-bda2-70f0be9dabd0
 Faulting package full name:
 Faulting package-relative application ID:
 }}}

 It seems to be related to windows 10 updates but I do every time the
 procedure: uninstall-install of dvorak-programming keyboard layout.

 ---
 WBR, Vladimir Lomov

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #28616 [Core Tor/Tor]: TLS internal error running Tor 0.3.4.9 on Debian Buster (OpenSSL 1.1.1a)

[Tor Bug Tracker & Wiki]

#28616: TLS internal error running Tor 0.3.4.9 on Debian Buster (OpenSSL 1.1.1a)
--+--
 Reporter:  filippo   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Component:  Core Tor/Tor
  Version:  Tor: 0.3.4.9  |   Severity:  Normal
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
 Running a simple Tor relay on Debian Buster seems to report TLS 1.3
 related OpenSSL internal errors. Not entirely sure how a function named
 tls13_hkdf_expand can fail, but I'm sure OpenSSL found a way.

 {{{
 Nov 26 01:07:40.000 [warn] Unhandled OpenSSL errors found at
 ../src/common/buffers_tls.c:65:
 Nov 26 01:07:40.000 [warn] TLS error: internal error (in SSL
 routines:tls13_hkdf_expand:---)
 }}}

 {{{
 FROM debian:buster
 ENV DEBIAN_FRONTEND noninteractive

 RUN apt-get update && apt-get install -y apt-transport-https gnupg ca-
 certificates

 RUN echo "deb https://deb.torproject.org/torproject.org buster main" >
 /etc/apt/sources.list.d/tor.list
 RUN echo "deb-src https://deb.torproject.org/torproject.org buster main"
 >> /etc/apt/sources.list.d/tor.list

 RUN gpg --no-tty --keyserver keys.gnupg.net --recv
 A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89
 RUN gpg --no-tty --export A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89 | apt-
 key add -

 RUN apt-get update && apt-get install -y tor deb.torproject.org-keyring
 nyx

 ADD torrc /etc/tor/torrc

 RUN useradd --user-group --system --create-home tor
 USER tor

 RUN mkdir -p /home/tor/.tor/keys
 VOLUME /home/tor/.tor

 EXPOSE 9001

 ENTRYPOINT ["tor"]
 }}}

 {{{
 Nov 26 01:07:27.114 [notice] Tor 0.3.4.9 (git-de9ea9f0dfc5ecae) running on
 Linux with Libevent 2.1.8-stable, OpenSSL 1.1.1a, Zlib 1.2.11, Liblzma
 5.2.2, and Libzstd 1.3.5.
 Nov 26 01:07:27.114 [notice] Tor can't help you if you use it wrong! Learn
 how to be safe at https://www.torproject.org/download/download#warning
 Nov 26 01:07:27.115 [notice] Read configuration file "/etc/tor/torrc".
 Nov 26 01:07:27.117 [notice] Based on detected system memory,
 MaxMemInQueues is set to 5767 MB. You can override this by setting
 MaxMemInQueues by hand.
 Nov 26 01:07:27.118 [notice] Scheduler type KIST has been enabled.
 Nov 26 01:07:27.118 [notice] Opening OR listener on 0.0.0.0:
 Nov 26 01:07:31.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.
 Nov 26 01:07:31.000 [notice] Parsing GEOIP IPv6 file
 /usr/share/tor/geoip6.
 Nov 26 01:07:31.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.
 Nov 26 01:07:31.000 [notice] Your Tor server's identity key fingerprint is
 'ToBeAnnounced 2EC042F4274CC8A54381C78E8D1BF322FA26A095'
 Nov 26 01:07:31.000 [notice] Bootstrapped 0%: Starting
 Nov 26 01:07:39.000 [notice] Starting with guard context "default"
 Nov 26 01:07:39.000 [notice] Bootstrapped 5%: Connecting to directory
 server
 Nov 26 01:07:39.000 [notice] Bootstrapped 10%: Finishing handshake with
 directory server
 Nov 26 01:07:39.000 [notice] Bootstrapped 50%: Loading relay descriptors
 Nov 26 01:07:40.000 [warn] Unhandled OpenSSL errors found at
 ../src/common/buffers_tls.c:65:
 Nov 26 01:07:40.000 [warn] TLS error: internal error (in SSL
 routines:tls13_hkdf_expand:---)
 Nov 26 01:07:40.000 [notice] I learned some more directory information,
 but not enough to build a circuit: We're missing descriptors for 1/2 of
 our primary entry guards (total microdescriptors: 5519/6239).
 Nov 26 01:07:41.000 [notice] I learned some more directory information,
 but not enough to build a circuit: We're missing descriptors for 1/2 of
 our primary entry guards (total microdescriptors: 5506/6327).
 Nov 26 01:07:42.000 [warn] Unhandled OpenSSL errors found at
 ../src/common/buffers_tls.c:65:
 Nov 26 01:07:42.000 [warn] TLS error: internal error (in SSL
 routines:tls13_hkdf_expand:---)
 Nov 26 01:07:49.000 [notice] Bootstrapped 80%: Connecting to the Tor
 network
 Nov 26 01:07:50.000 [notice] Bootstrapped 85%: Finishing handshake with
 first hop
 Nov 26 01:07:50.000 [notice] Bootstrapped 90%: Establishing a Tor circuit
 Nov 26 01:07:51.000 [notice] Tor has successfully opened a circuit. Looks
 like client functionality is working.
 Nov 26 01:07:51.000 [notice] Bootstrapped 100%: Done
 }}}

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #28611 [Core Tor/Tor]: Add `-mstack-protector-guard=global` to CFLAGS instead of `--disable-gcc-hardening` configure option on Windows?

[Tor Bug Tracker & Wiki]

#28611: Add `-mstack-protector-guard=global` to CFLAGS instead of 
`--disable-gcc-
hardening` configure option on Windows?
-+-
 Reporter:  grj  |  Owner:  (none)
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.0.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  029-backport 033-backport|  Actual Points:
  034-backport 035-backport win32|
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * keywords:   => 029-backport 033-backport 034-backport 035-backport win32
 * milestone:   => Tor: 0.4.0.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] #28614 [Core Tor/Tor]: Can't parse networkstatus consensus time

[Tor Bug Tracker & Wiki]

#28614: Can't parse networkstatus consensus time
--+
 Reporter:  Vort  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.4.0.x-final
Component:  Core Tor/Tor  |Version:  Tor: 0.3.5.5-alpha
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by nickm):

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


Comment:

 Hm. Does this happen with older versions of Tor, or is it a regression
 with this one?

 To me it sounds like the issue is with the \r at the end of the line --
 like the consensus file was saved in a windows text format, but it's being
 interpreted as a unix-style text format.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #28613 [Core Tor/Tor]: Log is filled with OpenSSL errors

[Tor Bug Tracker & Wiki]

#28613: Log is filled with OpenSSL errors
--+
 Reporter:  Vort  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.4.0.x-final
Component:  Core Tor/Tor  |Version:  Tor: 0.3.5.5-alpha
 Severity:  Normal| Resolution:
 Keywords:  ssl 035-backport  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by nickm):

 * keywords:  ssl => ssl 035-backport
 * milestone:   => Tor: 0.4.0.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] #28610 [Core Tor/Tor]: will WTF-PAD impair bandwidth scanning?

[Tor Bug Tracker & Wiki]

#28610: will WTF-PAD impair bandwidth scanning?
--+
 Reporter:  starlight |  Owner:  (none)
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.4.0.x-final
Component:  Core Tor/Tor  |Version:  Tor: unspecified
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by nickm):

 * cc: asn, mikeperry (added)
 * milestone:   => Tor: 0.4.0.x-final


Comment:

 I wouldn't think that it would have any effect, but I've added mike and
 asn to the cc.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #18098 [Core Tor/Tor]: prop224: Implement tor-genkey tool for offline HS key creation

[Tor Bug Tracker & Wiki]

#18098: prop224: Implement tor-genkey tool for offline HS key creation
--+
 Reporter:  dgoulet   |  Owner:  haxxpop
 Type:  enhancement   | Status:  needs_revision
 Priority:  Medium|  Milestone:  Tor: 0.4.0.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tor-hs|  Actual Points:
Parent ID:| Points:  6
 Reviewer:|Sponsor:  SponsorR-can
--+
Changes (by nickm):

 * milestone:  Tor: unspecified => Tor: 0.4.0.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] #28335 [Core Tor/Tor]: Make most periodic events turn themselves off when Tor is dormant, sleeping, etc.

[Tor Bug Tracker & Wiki]

#28335: Make most periodic events turn themselves off when Tor is dormant,
sleeping, etc.
--+
 Reporter:  nickm |  Owner:  nickm
 Type:  enhancement   | Status:  needs_review
 Priority:  Medium|  Milestone:  Tor: 0.4.0.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tor-mainloop  |  Actual Points:
Parent ID:  #25500| Points:  10
 Reviewer:  dgoulet   |Sponsor:  Sponsor8
--+

Comment (by nickm):

 Whoops!  See branch `dormant_v2` with PR at
 https://github.com/torproject/tor/pull/523

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #19566 [Core Tor/Tor]: SR: Use BUG() instead of tor_assert() when we can

[Tor Bug Tracker & Wiki]

#19566: SR: Use BUG() instead of tor_assert() when we can
-+-
 Reporter:  dgoulet  |  Owner:  dgoulet
 Type:  enhancement  | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.0.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Minor| Resolution:
 Keywords:  tor-sr, dirauth, easy, disaster- |  Actual Points:
  waiting-to-happen, 034-triage-20180328,|
  034-removed-20180328 035-backport  |
Parent ID:   | Points:  0.2
 Reviewer:  dgoulet  |Sponsor:
-+-
Changes (by nickm):

 * keywords:
 tor-sr, dirauth, easy, disaster-waiting-to-happen,
 034-triage-20180328, 034-removed-20180328
 =>
 tor-sr, dirauth, easy, disaster-waiting-to-happen,
 034-triage-20180328, 034-removed-20180328 035-backport
 * milestone:  Tor: unspecified => Tor: 0.4.0.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] #27503 [Applications/Tor Browser]: Disabling accessibility on Windows breaks screen readers

[Tor Bug Tracker & Wiki]

#27503: Disabling accessibility on Windows breaks screen readers
+--
 Reporter:  gk  |  Owner:  tbb-team
 Type:  defect  | Status:
|  needs_information
 Priority:  High|  Milestone:
Component:  Applications/Tor Browser|Version:
 Severity:  Normal  | Resolution:
 Keywords:  tbb-8.0-issues, tbb-regression  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--

Comment (by onionsoup):

 Thank you for working on this! Tor button and browser controls are now
 accessible again. However, it appears that web content is not being
 exposed to the screen reader, so where the website should be rendered,
 there's just something called "unknown". I'm not sure what the cause of
 that is, but it is across all sites. I tested with about:tor, youtube and
 wikipedia. I tested with Windows 7 using NVDA as a screen reader. To
 summarise, screen reader users cannot interact with websites, but
 everything that is not web content works.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #28495 [Core Tor/Stem]: Please provide a parser for detached signatures

[Tor Bug Tracker & Wiki]

#28495: Please provide a parser for detached signatures
---+---
 Reporter:  irl|  Owner:  atagar
 Type:  enhancement| Status:  needs_information
 Priority:  Medium |  Milestone:
Component:  Core Tor/Stem  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---
Changes (by atagar):

 * status:  new => needs_information


Comment:

 Hi irl. Took a few days but just finished. Will this do the trick for ya?

 https://gitweb.torproject.org/stem.git/commit/?id=71593fc

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #28615 [Metrics/Library]: Additional @type annotation

[Tor Bug Tracker & Wiki]

#28615: Additional @type annotation
-+--
 Reporter:  atagar   |  Owner:  metrics-team
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Metrics/Library  |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+--
 Hi Karsten, would you mind if we add a few new @type annotations? Stem is
 getting the ability to parse detached signatures (#28495), and sometimes
 is called to parse individual router status entries.

 The way I've designed Stem expects that all descriptor types have a type
 annotation that users can provide to say 'please parse this as X'. As such
 I need to either make up my own annotations or (better!) ask for us to
 expand our official set.

 In particular I'm hoping for...

 {{{
 @type detached-signature 1.0

   Detached signature as per section 3.10 of the dir-spec,
   and downloadable for five minutes each hour via the
   '/tor/status-vote/next/consensus-signatures' resource.

 @type router-status-entry-2 1.0


   Individual router status entry from a v2 network status
   document.

 @type router-status-entry-3 1.0


   Individual router status entry from a v3 network status
   document.

 @type router-status-entry-micro-3 1.0


   Individual router status entry from a v3 microdescriptor
   network status document.
 }}}

 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] #28067 [Core Tor/Tor]: Annotations should be documented in dir-spec.txt

[Tor Bug Tracker & Wiki]

#28067: Annotations should be documented in dir-spec.txt
--+--
 Reporter:  rl1987|  Owner:  (none)
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by atagar):

 Actually, on reflection no reason to wait. Filed a separate issue
 requesting this: #28615

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #27503 [Applications/Tor Browser]: Disabling accessibility on Windows breaks screen readers

[Tor Bug Tracker & Wiki]

#27503: Disabling accessibility on Windows breaks screen readers
+--
 Reporter:  gk  |  Owner:  tbb-team
 Type:  defect  | Status:
|  needs_information
 Priority:  High|  Milestone:
Component:  Applications/Tor Browser|Version:
 Severity:  Normal  | Resolution:
 Keywords:  tbb-8.0-issues, tbb-regression  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by gk):

 * status:  new => needs_information


Comment:

 Could anyone being affected by this bug test the custom bundle below? It
 should have the fixes Jacek wrote for
 https://bugzilla.mozilla.org/show_bug.cgi?id=1430149 and is not exploding
 on my Windows 7 testing machine:

 https://people.torproject.org/~gk/testbuilds/torbrowser-install-win64-tbb-
 nightly_27503_en-US.exe
 https://people.torproject.org/~gk/testbuilds/torbrowser-install-win64-tbb-
 nightly_27503_en-US.exe.asc

 Note: you might have trouble connecting to the Tor network when starting
 up Tor Browser the first time. In that case, closing Tor Browser and
 starting it again should fix that (I am currently looking into providing a
 bug report for that behavior for the network folks).

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #28067 [Core Tor/Tor]: Annotations should be documented in dir-spec.txt

[Tor Bug Tracker & Wiki]

#28067: Annotations should be documented in dir-spec.txt
--+--
 Reporter:  rl1987|  Owner:  (none)
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by atagar):

 Minor ask if/when this is done: I'd appreciate if we add a @type for
 detached signatures and individual router status entries. The lack of a
 @type annotation for these makes them a bit clunkier for me to deal with
 (since stem users specify how they'd like to parse documents by providing
 a type string).

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #28614 [Core Tor/Tor]: Can't parse networkstatus consensus time

[Tor Bug Tracker & Wiki]

#28614: Can't parse networkstatus consensus time
+--
 Reporter:  Vort|  Owner:  (none)
 Type:  defect  | Status:  new
 Priority:  Medium  |  Component:  Core Tor/Tor
  Version:  Tor: 0.3.5.5-alpha  |   Severity:  Normal
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
 When I run `tor.exe -f torrc`, one of the first messages in log file is:
 `Nov 25 19:51:48.000 [warn] ISO time "2018-11-25 17:00:00\r" was
 unparseable`
 `Nov 25 19:51:48.000 [warn] Unable to parse networkstatus consensus`

 Version tested: 3741f9e5 on Windows 7 SP1 x64.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #28613 [Core Tor/Tor]: Log is filled with OpenSSL errors

[Tor Bug Tracker & Wiki]

#28613: Log is filled with OpenSSL errors
--+
 Reporter:  Vort  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:  Tor: 0.3.5.5-alpha
 Severity:  Normal| Resolution:
 Keywords:  ssl   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by Vort):

 * component:  - Select a component => 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

[tor-bugs] #28613 [- Select a component]: Log is filled with OpenSSL errors

[Tor Bug Tracker & Wiki]

#28613: Log is filled with OpenSSL errors
+--
 Reporter:  Vort|  Owner:  (none)
 Type:  defect  | Status:  new
 Priority:  Medium  |  Component:  - Select a component
  Version:  Tor: 0.3.5.5-alpha  |   Severity:  Normal
 Keywords:  ssl |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
 When I run `tor.exe -f torrc`, log file becomes filled with such lines:
 {{{
 Nov 25 19:51:46.000 [warn] Unhandled OpenSSL errors found at
 connection_or.c:1685:
 Nov 25 19:51:46.000 [warn] TLS error: internal error (in SSL
 routines:tls13_hkdf_expand:---)
 Nov 25 19:51:47.000 [warn] Unhandled OpenSSL errors found at
 buffers_tls.c:69:
 Nov 25 19:51:47.000 [warn] TLS error: internal error (in SSL
 routines:tls13_hkdf_expand:---)
 }}}
 Version tested: 3741f9e5 on Windows 7 SP1 x64, configured with `--disable-
 gcc-hardening` and compiled by MSYS2 with following libraries: Libevent
 2.1.8-stable, OpenSSL 1.1.1a, Zlib 1.2.11, Liblzma 5.2.4, and Libzstd
 1.3.7.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #28612 [Core Tor/Tor]: Tor start via Windows service fails

[Tor Bug Tracker & Wiki]

#28612: Tor start via Windows service fails
+--
 Reporter:  Vort|  Owner:  (none)
 Type:  defect  | Status:  new
 Priority:  Medium  |  Component:  Core Tor/Tor
  Version:  Tor: 0.3.5.5-alpha  |   Severity:  Normal
 Keywords:  windows nt-service  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
 When I run `tor --service start` with latest Tor version (0.3.5.5-alpha or
 3741f9e5) on Windows 7 SP1 x64, Tor process starts, outputs some info into
 log file and exits (crashes?).
 Latest line in log file: `Nov 25 19:35:20.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.`
 Tor was configured with `--disable-gcc-hardening` and compiled by MSYS2
 with following libraries: Libevent 2.1.8-stable, OpenSSL 1.1.1a, Zlib
 1.2.11, Liblzma 5.2.4, and Libzstd 1.3.7.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #26770 [Core Tor/Tor]: Implement proposal 293: "Other ways for relays to know when to publish"

[Tor Bug Tracker & Wiki]

#26770: Implement proposal 293: "Other ways for relays to know when to publish"
-+-
 Reporter:  nickm|  Owner:  nickm
 Type:  enhancement  | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.0.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  prop293, prop275, 040-roadmap-   |  Actual Points:
  proposed   |
Parent ID:  #21642   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * status:  accepted => needs_review
 * milestone:  Tor: unspecified => Tor: 0.4.0.x-final


Comment:

 See my branch `prop293` with PR at
 https://github.com/torproject/tor/pull/542 .

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #26770 [Core Tor/Tor]: Implement proposal 293: "Other ways for relays to know when to publish"

[Tor Bug Tracker & Wiki]

#26770: Implement proposal 293: "Other ways for relays to know when to publish"
-+-
 Reporter:  nickm|  Owner:  nickm
 Type:  enhancement  | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.0.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  prop293, prop275, 040-roadmap-   |  Actual Points:  .1
  proposed   |
Parent ID:  #21642   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * actualpoints:   => .1


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

Re: [tor-bugs] #26770 [Core Tor/Tor]: Implement proposal 293: "Other ways for relays to know when to publish"

[Tor Bug Tracker & Wiki]

#26770: Implement proposal 293: "Other ways for relays to know when to publish"
-+-
 Reporter:  nickm|  Owner:  nickm
 Type:  enhancement  | Status:
 |  accepted
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  prop293, prop275, 040-roadmap-   |  Actual Points:
  proposed   |
Parent ID:  #21642   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

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


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