Re: [tor-bugs] #25333 [Applications/Tor Browser]: NOT SECURE CONECTION please help

[Tor Bug Tracker & Wiki]

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

Comment (by gk):

 So, we have a bunch of similar looking report in our bug track and on our
 mailing list. I already asked on the latter
 (https://lists.torproject.org/pipermail/tor-
 talk/2018-February/044017.html) whether the reporter might have an
 antivirus/firewall tool that could be interfering with TLS traffic. If so,
 could any of you please uninstall it and report back whether that solved
 your problem?

 There has not been a Tor Browser or Tor release in the last couple of
 weeks that could cause this. HTTPS Everywhere got updated last time on Jan
 29 which is a while back as well and disabling it does not seem to solve
 the problem.

 Thus, I suspect something on your local computer is messing with Tor
 Browser's TLS traffic.

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

Re: [tor-bugs] #25333 [Applications/Tor Browser]: NOT SECURE CONECTION please help

[Tor Bug Tracker & Wiki]

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

 * cc: mcs, brade (added)


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

Re: [tor-bugs] #25326 [Applications/Tor Browser]: connesisone sicura non riuscita

[Tor Bug Tracker & Wiki]

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

 * status:  needs_information => closed
 * version:  Tor: unspecified =>
 * resolution:   => duplicate


Comment:

 Sounds like a duplicate of #25333, Toruser85, please provide the
 information we need from you there, 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] #25333 [Applications/Tor Browser]: NOT SECURE CONECTION please help

[Tor Bug Tracker & Wiki]

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

 * cc: Toruser85 (added)


Comment:

 #25326 is a duplicate.

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

Re: [tor-bugs] #25333 [Applications/Tor Browser]: NOT SECURE CONECTION please help

[Tor Bug Tracker & Wiki]

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

 * cc: ATOMShadow (added)


Comment:

 Resolved #25325 as duplicate

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

Re: [tor-bugs] #25325 [Applications/Tor Browser]: Secure Connection Failed

[Tor Bug Tracker & Wiki]

#25325: Secure Connection Failed
--+---
 Reporter:  ATOMShadow|  Owner:  tbb-team
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:  duplicate
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---
Changes (by gk):

 * owner:  (none) => tbb-team
 * component:  - Select a component => Applications/Tor Browser
 * status:  new => closed
 * resolution:   => duplicate


Comment:

 I guess that's the same issue as other folks have been reporting in a
 number of tickets. Let's have the discussion in #25333.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #9413 [Archived/Vidalia]: The proxy server is refusing connections

[Tor Bug Tracker & Wiki]

#9413: The proxy server is refusing connections
-+-
 Reporter:  Cruzax   |  Owner:  chiiph
 Type:  defect   | Status:  closed
 Priority:  Immediate|  Milestone:  TorBrowserBundle
 |  2.3.x-stable
Component:  Archived/Vidalia |Version:  Tor: 0.2.3.25
 Severity:  Normal   | Resolution:  wontfix
 Keywords:  TorBrowserBundle,|  Actual Points:
  Vidalia, Tor Launcher, SocksPort,  |
  ControlPort|
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by gk):

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


Comment:

 Vidalia is long gone.

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

Re: [tor-bugs] #25333 [Applications/Tor Browser]: NOT SECURE CONECTION please help

[Tor Bug Tracker & Wiki]

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

 * cc: mario (added)
 * component:  Core Tor/Tor => Applications/Tor Browser


Comment:

 #25337 is a duplicate.

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

Re: [tor-bugs] #25337 [Applications/Tor Browser]: secure connection failed

[Tor Bug Tracker & Wiki]

#25337: secure connection failed
--+---
 Reporter:  mario |  Owner:  (none)
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:  duplicate
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---
Changes (by gk):

 * status:  needs_information => closed
 * component:  Webpages => Applications/Tor Browser
 * resolution:   => duplicate


Comment:

 Duplicate of #25333.

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

Re: [tor-bugs] #16472 [Applications/Tor Browser]: Upgrade Binutils to 2.25+ for Tor Browser builds

[Tor Bug Tracker & Wiki]

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

Comment (by gk):

 boklm: could you test the selfrando commit
 d2951ac1d3747a4d8a9ef222d38d2d13e5ae2ba9 and report back whether that
 solved our problems? ahomescu said we should be good with that one.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #12959 [HTTPS Everywhere/EFF-HTTPS Everywhere]: Google APIs breaks www.mojasvadba.sk

[Tor Bug Tracker & Wiki]

#12959: Google APIs breaks www.mojasvadba.sk
---+--
 Reporter:  cypherpunks|  Owner:  zyan
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  HTTPS Everywhere/EFF-HTTPS Everywhere  |Version:
 Severity:  Normal | Resolution:
 Keywords:  httpse-ruleset-bug |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--
Changes (by cypherpunks):

 * parent:  #12384 =>


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #12384 [HTTPS Everywhere/EFF-HTTPS Everywhere]: Google APIs rule breaks this website

[Tor Bug Tracker & Wiki]

#12384: Google APIs rule breaks this website
-+-
 Reporter:  NewEraCracker|  Owner:  zyan
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  HTTPS Everywhere/EFF-HTTPS   |Version:
  Everywhere |
 Severity:  Normal   | Resolution:  fixed
 Keywords:  httpse-ruleset-bug   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by cypherpunks):

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


Comment:

 Fixed by https://github.com/EFForg/https-everywhere/pull/14697

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25024 [Core Tor/Tor]: Add optional spell check to makefile to check for typos in tor source code.

[Tor Bug Tracker & Wiki]

#25024: Add optional spell check to makefile to check for typos in tor source 
code.
--+
 Reporter:  fristonio |  Owner:  alison
 Type:  enhancement   | Status:  needs_review
 Priority:  Low   |  Milestone:  Tor: 0.3.4.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Minor | Resolution:
 Keywords:  tor-comment   |  Actual Points:
Parent ID:| Points:  0.5
 Reviewer:|Sponsor:
--+
Changes (by teor):

 * status:  needs_revision => needs_review


Comment:

 Hi, sorry this hasn't been reviewed, it didn't have the right status for
 our review groups to pick it up. It should be reviewed in the next few
 weeks.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25331 [Applications/Tor Browser]: Test from #18912 failing

[Tor Bug Tracker & Wiki]

#25331: Test from #18912 failing
--+---
 Reporter:  arthuredelstein   |  Owner:  tbb-team
 Type:  defect| Status:  needs_information
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---

Comment (by mcs):

 Replying to [comment:4 arthuredelstein]:
 > So my question is, does it matter that we're getting a different error
 code? I am wondering whether any error code will do, or if we need
 MOZILLA_PKIX_ERROR_KEY_PINNING_FAILURE specifically. (I'm probably still
 naive about the design of the test.)

 It probably does not matter too much, although it is designed to look
 specifically for a pinning failure. Let me think about what to do.

 > I haven't figured out what this new error code, `2153394164` is intended
 to mean. I guess the next step for me might be to try to use gdb to track
 down where the old and new error codes are coming from.

 Yes, although I don't know how much work that will be. Let me know if you
 want me to make an attempt (although I won't get to it until next week at
 this point). The new error code is `0x805A2FF4` which is
 `SSL_ERROR_BAD_CERT_DOMAIN` so it isn't too far off in terms of the
 expected error. But I think we should dive deep enough to understand what
 is happening.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #7679 [Core Tor/Tor]: Test integration of Minion (out-of-order data transmission thing) with Tor relays

[Tor Bug Tracker & Wiki]

#7679: Test integration of Minion (out-of-order data transmission thing) with 
Tor
relays
--+--
 Reporter:  arma  |  Owner:  (none)
 Type:  project   | Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tor-relay |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by cypherpunks):

 It has been five years since Minion has been published, and despite a
 handful of reports and papers showing it as a good project, we don't even
 see a single patch! Nor they have the intention to release any code or
 patches.

 Does they really want to cooperate with the community, or simply marketing
 about their research for their own career, while hide their patches as
 their "intellectual property"?

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

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

[Tor Bug Tracker & Wiki]

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

 * reviewer:   => isis


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25074 [Core Tor/Tor]: TROVE-2018-001

[Tor Bug Tracker & Wiki]

#25074: TROVE-2018-001
---+---
 Reporter:  teor   |  Owner:  nickm
 Type:  defect | Status:  needs_review
 Priority:  Medium |  Milestone:  Tor:
   |  0.3.3.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  033-must, review-group-33  |  Actual Points:
Parent ID: | Points:
 Reviewer:  catalyst   |Sponsor:
---+---
Changes (by catalyst):

 * reviewer:   => catalyst


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25337 [Webpages]: secure connection failed

[Tor Bug Tracker & Wiki]

#25337: secure connection failed
--+---
 Reporter:  mario |  Owner:  (none)
 Type:  defect| Status:  needs_information
 Priority:  Medium|  Milestone:
Component:  Webpages  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---

Comment (by mario):

 thanks for your reply Jaruga
 Yes you're correct http is OK
 the symptoms are the same of
 https://trac.torproject.org/projects/tor/ticket/25333

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

Re: [tor-bugs] #25308 [Core Tor]: Onion service node pinning by default

[Tor Bug Tracker & Wiki]

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

Comment (by asn):

 We are consdering doing this but it's a lot of work. It's basically
 proposal 247 but it needs lots of work to make it work well if the whole
 network uses it.

 I can't think of a great fingerprinting danger if only a few people have
 node pinning enabled. The guard can figure this out, but if the attacker
 is your guard then you are fucked anyway. The pinned nodes can also figure
 it out, but I guess you are pinning them because you trust them. A local
 area adversary should not be able to distinguish something significant.
 Please correct me if I'm wrong

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

Re: [tor-bugs] #25331 [Applications/Tor Browser]: Test from #18912 failing

[Tor Bug Tracker & Wiki]

#25331: Test from #18912 failing
--+---
 Reporter:  arthuredelstein   |  Owner:  tbb-team
 Type:  defect| Status:  needs_information
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---

Comment (by arthuredelstein):

 So my question is, does it matter that we're getting a different error
 code? I am wondering whether any error code will do, or if we need
 MOZILLA_PKIX_ERROR_KEY_PINNING_FAILURE specifically. (I'm probably still
 naive about the design of the test.)

 I haven't figured out what this new error code, `2153394164` is intended
 to mean. I guess the next step for me might be to try to use gdb to track
 down where the old and new error codes are coming from.

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

Re: [tor-bugs] #25188 [Core Tor/Tor]: Spec bug in formal definition of Document in dir-spec.txt

[Tor Bug Tracker & Wiki]

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

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

[Tor Bug Tracker & Wiki]

#25331: Test from #18912 failing
--+---
 Reporter:  arthuredelstein   |  Owner:  tbb-team
 Type:  defect| Status:  needs_information
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---

Comment (by arthuredelstein):

 I built `tor-browser.git` and confirmed in about:config that
 `security.nocertdb` is set to true.

 Then I ran the same 3 tests as before:
 {{{
 ./mach mochitest
 toolkit/mozapps/update/tests/chrome/test_0790_check_certPinning_noUpdate.xul
 }}}
 gave
 {{{
 56 INFO TEST-UNEXPECTED-FAIL |
 toolkit/mozapps/update/tests/chrome/test_0790_check_certPinning_noUpdate.xul
 | Checking update.errorCode == MOZILLA_PKIX_ERROR_KEY_PINNING_FAILURE -
 got 2153390067, expected 2153398272
 }}}
 Then
 {{{
 ./mach mochitest --setpref=security.nocertdb=false
 toolkit/mozapps/update/tests/chrome/test_0790_check_certPinning_noUpdate.xul
 }}}
 resulted in all tests passing. Finally,
 {{{
 ./mach mochitest --setpref=security.nocertdb=true
 toolkit/mozapps/update/tests/chrome/test_0790_check_certPinning_noUpdate.xul
 }}}
 gave the result
 {{{
 56 INFO TEST-UNEXPECTED-FAIL |
 toolkit/mozapps/update/tests/chrome/test_0790_check_certPinning_noUpdate.xul
 | Checking update.errorCode == MOZILLA_PKIX_ERROR_KEY_PINNING_FAILURE -
 got 2153390067, expected 2153398272
 }}}
 So to analyze: my observation in the description `tor-
 browser-52.6.0esr-8.0-2` was irrelevant because I had left
 `security.nocertdb=true` (Both branches give the same unexpected error
 code of `2153390067`, but that's not very relevant.). If we look at
 `security.nocertdb=false` only, then I see that the test passes for `tor-
 browser-52.6.0esr-8.0-2` but it fails on top of `mozilla-central` with a
 different unexpected error code of `2153394164`.

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

[Tor Bug Tracker & Wiki]

#24857: tor 0.3.1.9 100% cpu load
-+
 Reporter:  Eugene646|  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor: 0.3.4.x-final
Component:  Core Tor/Tor |Version:  Tor: 0.3.2.9
 Severity:  Normal   | Resolution:
 Keywords:  cpu, windows, linux  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+

Comment (by cypherpunks):

 https://tor.stackexchange.com/questions/16714/windows-10-tor-relay-
 use-100-cpu

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

Re: [tor-bugs] #25321 [Applications/Tor Browser]: Unable to comment on independent.co.uk

[Tor Bug Tracker & Wiki]

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

Comment (by Jaruga):

 If you can't log in at all without any formal notice (i.e. No "We no
 longer allow Tor connections" notifier, simply a reloaded blank login
 form, etc) I would imagine that it has to do with either your cookies or
 referrer settings. Have you tweaked the internals in about:config? How are
 you configuring NoScript?

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

Re: [tor-bugs] #25326 [Applications/Tor Browser]: connesisone sicura non riuscita

[Tor Bug Tracker & Wiki]

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

 * cc: brade, mcs (added)
 * status:  new => needs_information


Comment:

 Hi.  Unfortunately I do not speak Italian so please forgive any
 misunderstanding as I am using translate.google.com and it is not perfect:
   after starting any search, web pages or update I try to do it appears to
 me secure connection error. In a nutshell without anything being changed
 last week it worked perfectly

 1) Are you on Windows, Mac or Linux? What is your OS version?
 2) What version of Tor Browser are you using?
 3) Are you able to use other browsers (is only Tor Browser broken)?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25337 [Webpages]: secure connection failed

[Tor Bug Tracker & Wiki]

#25337: secure connection failed
--+---
 Reporter:  mario |  Owner:  (none)
 Type:  defect| Status:  needs_information
 Priority:  Medium|  Milestone:
Component:  Webpages  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---
Changes (by Jaruga):

 * status:  new => needs_information


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

Re: [tor-bugs] #25337 [Webpages]: secure connection failed

[Tor Bug Tracker & Wiki]

#25337: secure connection failed
--+
 Reporter:  mario |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Webpages  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by Jaruga):

 Possibly related: https://trac.torproject.org/projects/tor/ticket/25333

 So am I correct to deduct that it is only HTTPS sites that are not working
 for you, but http remains functional?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24256 [Metrics/Onionoo]: Add a new "outdated" field to distinguish between outdated and too new tor versions

[Tor Bug Tracker & Wiki]

#24256: Add a new "outdated" field to distinguish between outdated and too new 
tor
versions
-+--
 Reporter:  arma |  Owner:  karsten
 Type:  enhancement  | Status:  needs_review
 Priority:  Medium   |  Milestone:
Component:  Metrics/Onionoo  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:  #25199   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by cypherpunks):

 actually, by the version spec 0.2.5.16-dev is "new in series"

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24256 [Metrics/Onionoo]: Add a new "outdated" field to distinguish between outdated and too new tor versions

[Tor Bug Tracker & Wiki]

#24256: Add a new "outdated" field to distinguish between outdated and too new 
tor
versions
-+--
 Reporter:  arma |  Owner:  karsten
 Type:  enhancement  | Status:  needs_review
 Priority:  Medium   |  Milestone:
Component:  Metrics/Onionoo  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:  #25199   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by cypherpunks):

 {{{
  398 {"version":"0.2.5.16","version_status":"recommended"},
1 {"version":"0.2.5.16-dev","version_status":"unrecommended"},
 }}}

 it matches the spec but I find the spec strange and counterintuitive
 if 0.2.5.16 is recommended I would declare 0.2.5.16-dev experimental,
 but I guess the spec will not be changed.

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

Re: [tor-bugs] #25333 [Core Tor/Tor]: NOT SECURE CONECTION please help

[Tor Bug Tracker & Wiki]

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

Comment (by Jaruga):

 Possibly related solution:
 https://trac.torproject.org/projects/tor/ticket/9413

 Firstly, I cannot replicate this bug. I would assume it's due to your
 local configuration to some capacity.

 It would help if you supplied more information with your initial ticket,
 the issue could be anything from firewalls to buggy add-ons. It's unlikely
 to be HTTPS-E, however testing it is as simple as turning off HTTPS-
 Everywhere and attempting to load Google or similar. If the problem
 persists then you can rule that out.

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

Re: [tor-bugs] #25325 [- Select a component]: Secure Connection Failed

[Tor Bug Tracker & Wiki]

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

Comment (by Jaruga):

 Are you using a bridge?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24256 [Metrics/Onionoo]: Add a new "outdated" field to distinguish between outdated and too new tor versions

[Tor Bug Tracker & Wiki]

#24256: Add a new "outdated" field to distinguish between outdated and too new 
tor
versions
-+--
 Reporter:  arma |  Owner:  karsten
 Type:  enhancement  | Status:  needs_review
 Priority:  Medium   |  Milestone:
Component:  Metrics/Onionoo  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:  #25199   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by karsten):

 * status:  accepted => needs_review


Comment:

 Please review
 
[https://gitweb.torproject.org/user/karsten/onionoo.git/commit/?h=task-24256=6dd9709751d898e17e1b76e44b9d3412b6e8678d
 commit 6dd9709 in my task-24256 branch].

 Here's what this branch produces when run locally:

 {{{
 $ curl
 "http://localhost:8080/details?fields=version,version_status=relay; |
 sort | uniq -c
   % Total% Received % Xferd  Average Speed   TimeTime Time
 Current
  Dload  Upload   Total   SpentLeft
 Speed
 100  391k0  391k0 0   193k  0 --:--:--  0:00:02 --:--:--
 193k
1 "bridges":[
1 "bridges_published":"2018-02-22 19:04:06",
1 "build_revision":"6dd9709",
1 "relays":[
1 "relays_published":"2018-02-22 19:00:00",
1 ],
1 ]}
2 {"version":"0.2.4.19","version_status":"obsolete"},
   15 {"version":"0.2.4.20","version_status":"obsolete"},
5 {"version":"0.2.4.21","version_status":"obsolete"},
9 {"version":"0.2.4.22","version_status":"obsolete"},
  148 {"version":"0.2.4.23","version_status":"obsolete"},
9 {"version":"0.2.4.24","version_status":"obsolete"},
   81 {"version":"0.2.4.27","version_status":"obsolete"},
   96 {"version":"0.2.4.29","version_status":"obsolete"},
   10 {"version":"0.2.5.10","version_status":"obsolete"},
   64 {"version":"0.2.5.12","version_status":"obsolete"},
   57 {"version":"0.2.5.14","version_status":"obsolete"},
2 {"version":"0.2.5.15","version_status":"obsolete"},
  398 {"version":"0.2.5.16","version_status":"recommended"},
1 {"version":"0.2.5.16-dev","version_status":"unrecommended"},
3 {"version":"0.2.6.0-alpha-dev","version_status":"unrecommended"},
   30 {"version":"0.2.6.10","version_status":"unrecommended"},
1 {"version":"0.2.6.7","version_status":"unrecommended"},
1 {"version":"0.2.6.8","version_status":"unrecommended"},
5 {"version":"0.2.6.9","version_status":"unrecommended"},
1 {"version":"0.2.7.1-alpha","version_status":"unrecommended"},
1 {"version":"0.2.7.2-alpha","version_status":"unrecommended"},
1 {"version":"0.2.7.4-rc","version_status":"unrecommended"},
3 {"version":"0.2.7.5","version_status":"unrecommended"},
  217 {"version":"0.2.7.6","version_status":"unrecommended"},
1 {"version":"0.2.8.10","version_status":"unrecommended"},
1 {"version":"0.2.8.10-dev","version_status":"unrecommended"},
5 {"version":"0.2.8.11","version_status":"unrecommended"},
6 {"version":"0.2.8.12","version_status":"unrecommended"},
2 {"version":"0.2.8.2-alpha","version_status":"unrecommended"},
2 {"version":"0.2.8.6","version_status":"unrecommended"},
7 {"version":"0.2.8.7","version_status":"unrecommended"},
   11 {"version":"0.2.8.8","version_status":"unrecommended"},
8 {"version":"0.2.8.9","version_status":"unrecommended"},
   72 {"version":"0.2.9.10","version_status":"unrecommended"},
  176 {"version":"0.2.9.11","version_status":"unrecommended"},
   40 {"version":"0.2.9.12","version_status":"unrecommended"},
   22 {"version":"0.2.9.13","version_status":"unrecommended"},
  893 {"version":"0.2.9.14","version_status":"recommended"},
   10 {"version":"0.2.9.8","version_status":"unrecommended"},
   32 {"version":"0.2.9.9","version_status":"unrecommended"},
2 {"version":"0.3.0.1-alpha","version_status":"unrecommended"},
  106 {"version":"0.3.0.10","version_status":"unrecommended"},
2 {"version":"0.3.0.11","version_status":"unrecommended"},
   90 {"version":"0.3.0.13","version_status":"unrecommended"},
2 {"version":"0.3.0.13-dev","version_status":"unrecommended"},
1 {"version":"0.3.0.4-rc","version_status":"unrecommended"},
1 {"version":"0.3.0.6-dev","version_status":"unrecommended"},
3 {"version":"0.3.0.7","version_status":"unrecommended"},
   10 {"version":"0.3.0.8","version_status":"unrecommended"},
   49 {"version":"0.3.0.9","version_status":"unrecommended"},
6 {"version":"0.3.1.2-alpha-dev","version_status":"unrecommended"},
1 {"version":"0.3.1.4-alpha","version_status":"unrecommended"},
1 {"version":"0.3.1.5-alpha","version_status":"unrecommended"},
  129 {"version":"0.3.1.7","version_status":"unrecommended"},
1 {"version":"0.3.1.7-dev","version_status":"unrecommended"},
   89 {"version":"0.3.1.8","version_status":"unrecommended"},
1 

Re: [tor-bugs] #25331 [Applications/Tor Browser]: Test from #18912 failing

[Tor Bug Tracker & Wiki]

#25331: Test from #18912 failing
--+---
 Reporter:  arthuredelstein   |  Owner:  tbb-team
 Type:  defect| Status:  needs_information
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---

Comment (by arthuredelstein):

 Thanks for looking into this!

 I ran some tests on top of your patch rebased on top of mozilla-central
 (https://github.com/arthuredelstein/tor-browser/1436226+2). First I ran
 `./mach run` and in the browser console I entered
 `Services.prefs.prefHasUserValue("security.nocertdb")` and got `false`.

 Then I ran the test as before:
 {{{
 ./mach mochitest
 toolkit/mozapps/update/tests/chrome/test_0790_check_certPinning_noUpdate.xul
 }}}
 and got
 {{{
   TEST-UNEXPECTED-FAIL |
 toolkit/mozapps/update/tests/chrome/test_0790_check_certPinning_noUpdate.xul
 | Checking update.errorCode == MOZILLA_PKIX_ERROR_KEY_PINNING_FAILURE. If
 removing or changing this test, please notify tbb-...@lists.torproject.org
 - got 2153394164, expected 2153398272
 }}}

 Next, I tried running the test with the --setpref flag as you suggested:
 {{{
 ./mach mochitest --setpref=security.nocertdb=false
 toolkit/mozapps/update/tests/chrome/test_0790_check_certPinning_noUpdate.xul
 }}}
 and the result I got was:
 {{{
   TEST-UNEXPECTED-FAIL |
 toolkit/mozapps/update/tests/chrome/test_0790_check_certPinning_noUpdate.xul
 | Checking update.errorCode == MOZILLA_PKIX_ERROR_KEY_PINNING_FAILURE. If
 removing or changing this test, please notify tbb-...@lists.torproject.org
 - got 2153394164, expected 2153398272
 SimpleTest.is@chrome://mochikit/content/tests/SimpleTest/SimpleTest.js:312:5
 
checkErrorCode@chrome://mochitests/content/chrome/toolkit/mozapps/update/tests/chrome/test_0790_check_certPinning_noUpdate.xul:61:3
 }}}

 I then tried setting the flag to true:

 {{{
 ./mach mochitest --setpref=security.nocertdb=true
 toolkit/mozapps/update/tests/chrome/test_0790_check_certPinning_noUpdate.xul
 }}}

 and I got:

 {{{
   TEST-UNEXPECTED-FAIL |
 toolkit/mozapps/update/tests/chrome/test_0790_check_certPinning_noUpdate.xul
 | Checking update.errorCode == MOZILLA_PKIX_ERROR_KEY_PINNING_FAILURE. If
 removing or changing this test, please notify tbb-...@lists.torproject.org
 - got 2153390067, expected 2153398272
 SimpleTest.is@chrome://mochikit/content/tests/SimpleTest/SimpleTest.js:312:5
 
checkErrorCode@chrome://mochitests/content/chrome/toolkit/mozapps/update/tests/chrome/test_0790_check_certPinning_noUpdate.xul:61:3
 }}}

 In sum, I think my build does not have Tor Browser pref settings, by
 default it should be operating equivalent to the pref being set to false.
 So when security.nocertdb is default or false, I get the unexpected error
 code of `2153394164` and when security.nocertdb is set to true, I get the
 unexpected error code of `2153390067`. Both error values are different
 from the expected error code `2153398272`.

 Next I'm going to try these same set of experiments on tor-browser.git.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25203 [Core Tor/Tor]: document max. value of SigningKeyLifetime

[Tor Bug Tracker & Wiki]

#25203: document max. value of SigningKeyLifetime
---+
 Reporter:  cypherpunks|  Owner:  (none)
 Type:  enhancement| Status:  new
 Priority:  Medium |  Milestone:  Tor: 0.3.4.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Minor  | Resolution:
 Keywords:  easy, tor-doc  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+
Changes (by nickm):

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


Comment:

 So, the "malformed or out of bounds" warning seems to happen if you
 specify *any* interval that's over INT_MAX seconds long [approx 68 years].
 I don't know whether it makes more sense to document that as a maximum for
 all the various intervals, or whether it makes more sense to treat super-
 long intervals for stuff like SigningKeyLifetime as meaning "forever".

 I don't have easy answers for the other questions; does anyone else?

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

Re: [tor-bugs] #25188 [Core Tor/Tor]: Spec bug in formal definition of Document in dir-spec.txt

[Tor Bug Tracker & Wiki]

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

Comment (by witchof0x20):

 I can't immediately think of an ambiguity that would be fixed by this, but
 would it be worth it to also say 'A Keyword cannot be "-END"'?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25337 [Webpages]: secure connection failed

[Tor Bug Tracker & Wiki]

#25337: secure connection failed
--+
 Reporter:  mario |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Webpages  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 I'm using 7.5 tor version 56.6.0 under windows10.
 tor starts regularly,but even if I attempt to link to the "Test Tor
 Network Settings" i receive the message secure connection failed.

 Secure Connection Failed

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

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




 restart a new circuit doesn't solve
 NO https website is working
 Thanks in advance for your help

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

Re: [tor-bugs] #25269 [Core Tor/Tor]: Set codegen-units to 1 in src/rust/Cargo.toml to eke out every last drop of performance

[Tor Bug Tracker & Wiki]

#25269: Set codegen-units to 1 in src/rust/Cargo.toml to eke out every last 
drop of
performance
--+
 Reporter:  cypherpunks   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  rust, easy|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by nickm):

 Do we have to do this in all of our Cargo.toml files, or is it enough to
 do it in the toplevel one?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #3940 [Core Tor/Tor]: Allow MapAddress .exit even if AllowDotExit is 0

[Tor Bug Tracker & Wiki]

#3940: Allow MapAddress .exit even if AllowDotExit is 0
-+-
 Reporter:  sjmurdoch|  Owner:  (none)
 Type:  defect   | Status:
 |  needs_review
 Priority:  High |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.2.32
 Severity:  Normal   | Resolution:
 Keywords:  regression tor-client 032-backport   |  Actual Points:
  031-backport 029-backport 033-must review- |
  group-33   |
Parent ID:   | Points:
 Reviewer:  nickm|Sponsor:
-+-
Changes (by nickm):

 * reviewer:   => nickm


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

Re: [tor-bugs] #25055 [Core Tor/Tor]: string_is_valid_hostname() returns true for IPv4 addresses

[Tor Bug Tracker & Wiki]

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

Comment (by rl1987):

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

[Tor Bug Tracker & Wiki]

#25330: Create email & LDAP for Heather
-+
 Reporter:  ewyatt   |  Owner:  tpa
 Type:  task | Status:  closed
 Priority:  High |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+
Changes (by nickm):

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


Comment:

 Okay, I think I did it.  Please let me know whether I did it right. :)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25109 [Webpages/Website]: Deactivate job posting on website (Chief Financial and Grants Officer)

[Tor Bug Tracker & Wiki]

#25109: Deactivate job posting on website (Chief Financial and Grants Officer)
--+
 Reporter:  ewyatt|  Owner:  (none)
 Type:  task  | Status:  closed
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by ewyatt):

 * 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] #25336 [Webpages/Website]: Please add job posting to website - Executive Director

[Tor Bug Tracker & Wiki]

#25336: Please add job posting to website - Executive Director
--+--
 Reporter:  ewyatt|  Owner:  hiro
 Type:  task  | Status:  assigned
 Priority:  Very High |  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by ewyatt):

 The posting was originally rejected for containing (the non-modified
 versions of) these two words: he[@]lthy and m[0]ney. Please correct these
 two things on the website posting. Thank you very much!

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25336 [Webpages/Website]: Please add job posting to website - Executive Director

[Tor Bug Tracker & Wiki]

#25336: Please add job posting to website - Executive Director
--+--
 Reporter:  ewyatt|  Owner:  hiro
 Type:  task  | Status:  assigned
 Priority:  Very High |  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 Hello,
 Please add the below job posting to our website under the title “
 Executive Director.” Thank you!

 {{{

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA512


 Internet Freedom Nonprofit Seeks Executive Director

 The Tor Project, Inc., is a 501(c)(3) organization headquartered in
 Seattle that provides the technical infrastructure for privacy protection
 over the Internet, helping millions of activists, journalists and others
 around the world communicate securely. With paid staff and contractors of
 around 35 engineers and operational support people, plus many volunteers
 all over the world who contribute to our work, the Tor Project is funded
 in part by government grants and contracts, as well as by individual,
 foundation, and corporate donations. Our mission is “To advance human
 rights and freedoms by creating and deploying free and open anonymity and
 privacy technologies, supporting their unrestricted availability and use,
 and furthering their scientific and popular understanding.”

 We are currently seeking an Executive Director to lead the organization
 into our next phase of growth and sustainability. This position can be
 based anywhere, as our work is international in scope. This person must be
 able to communicate regularly with the staff working on the ground at our
 organizational headquarters in Seattle. This position reports directly to
 the Tor Project Board of Directors.

 The Executive Director sets the tone for the organization, thinks
 strategically, and provides leadership and guidance in the day-to-day
 operations. The Tor Project does open source software development, and the
 Executive Director must be able to engage with various different
 stakeholders in managing the organization. Some of the key attributes of
 this person should be:

 •   A strong public commitment to privacy, and a good
 understanding of related debates.
 •   A good understanding of open source development culture,
 and a commitment to transparent organizations.
 •   A strong commitment to creating and maintaining a he@lthy
 and safe working environment, including for remote participants.
 •   A talent for consensus and community building.
 •   An ability to effectively support and collaborate with
 diverse groups of people.
 •   A willingness to share responsibility and leadership of
 the organization with a leadership team.
 •   An enthusiasm for coaching and developing emerging
 leaders.
 •   A natural leadership ability that encourages and empowers
 others to do their best work.
 •   Strong written and verbal communications skills.

 Some of the key requirements of this position are at least five years or
 equivalent experience in each of the following areas:

 •   Nonprofit fundraising, including raising m0ney from
 government contracts and grants, foundations, corporations and individual
 contributions;
 •   Talking to and working with the press, including being
 active and visible in promoting organizational goals and enhancing the
 organization’s image;
 •   Solid, hands-on, budget management skills, including
 budget preparation, analysis, decision-making and reporting;
 •   Human resource administration, including working with a
 leadership team and hiring and firing experience;
 •   Working closely with a board of directors;
 •   Non-profit operations, including managing an office and
 planning events, ideally remotely; and
 •   Running a corporation of at least $3 million in yearly
 revenue, including an ability to recognize when outside professional
 assistance is required.

 The successful candidate will have a global perspective on privacy and
 censorship issues and an ability to balance “survival issues” (like next
 year’s funding) with “mission issues” (like making sure we’re actually
 moving our programs in a good direction). This person will have the
 ability to work remotely and work with remote workers. To this end, this
 person must be willing to adapt to daily use of privacy enhancing
 technologies used to communicate with others. Prior experience working
 with software development or internet people is a plus.

 The Tor Project has made a commitment to being a safe, fair, and diverse
 workplace.  Our new Executive Director must be 

Re: [tor-bugs] #16472 [Applications/Tor Browser]: Upgrade Binutils to 2.25+ for Tor Browser builds

[Tor Bug Tracker & Wiki]

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

Comment (by cypherpunks):

 `--no-insert-timestamp`?

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

Re: [tor-bugs] #16472 [Applications/Tor Browser]: Upgrade Binutils to 2.25+ for Tor Browser builds

[Tor Bug Tracker & Wiki]

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

 * Attachment "tor-win32.diff" added.


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

Re: [tor-bugs] #16472 [Applications/Tor Browser]: Upgrade Binutils to 2.25+ for Tor Browser builds

[Tor Bug Tracker & Wiki]

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

Comment (by boklm):

 Replying to [comment:15 gk]:

 >
 > Have you checked about the deterministic output of the Windows bundles
 after the switch to the newer  binutils version? That has been the main
 reason for why an update did not happen earlier (see: comment:1).

 It seems it is not deterministic. I did two builds using branch
 `boklm/bug_16472_v3`, and have some differences in the Windows builds. I
 will attach the output of diffoscope on `tor-win32-0.3.3.2-alpha.zip`.

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

Re: [tor-bugs] #25188 [Core Tor/Tor]: Spec bug in formal definition of Document in dir-spec.txt

[Tor Bug Tracker & Wiki]

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

Comment (by witchof0x20):

 I attached a potential patch. How does this 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] #25188 [Core Tor/Tor]: Spec bug in formal definition of Document in dir-spec.txt

[Tor Bug Tracker & Wiki]

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

 * Attachment "fix_document_ambiguity.patch" added.

 Patch for this issue

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

Re: [tor-bugs] #25314 [Applications/Tor Mail]: Build error during Windows (32- and 64-bit builds) of Thunderbird

[Tor Bug Tracker & Wiki]

#25314: Build error during Windows (32- and 64-bit builds) of Thunderbird
---+
 Reporter:  sukhbir|  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Applications/Tor Mail  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+

Comment (by sukhbir):

 Patch; I am keeping it separate for now but since I will submit this
 upstream as well, I will combine it later.

 In comm-esr52:

 {{{
 diff --git a/mailnews/base/search/src/nsMsgImapSearch.cpp
 b/mailnews/base/search/src/nsMsgImapSearch.cpp
 --- a/mailnews/base/search/src/nsMsgImapSearch.cpp
 +++ b/mailnews/base/search/src/nsMsgImapSearch.cpp
 @@ -84,7 +84,7 @@

  nsresult nsMsgSearchOnlineMail::Encode (nsCString& pEncoding,
  nsISupportsArray *searchTerms,
 -const char16_t *destCharset)
 +char16ptr_t destCharset)
  {
nsCString imapTerms;

 diff --git a/mailnews/base/search/src/nsMsgSearchImap.h
 b/mailnews/base/search/src/nsMsgSearchImap.h
 --- a/mailnews/base/search/src/nsMsgSearchImap.h
 +++ b/mailnews/base/search/src/nsMsgSearchImap.h
 @@ -24,7 +24,7 @@

static nsresult Encode (nsCString& ppEncoding,
  nsISupportsArray *searchTerms,
 -const char16_t *destCharset);
 +char16ptr_t destCharset);


  protected:
 }}}

 And in mozilla/ (tor-browser-52.6.0esr-7.5-2-build1):

 {{{
 diff --git a/xpcom/glue/nsCRTGlue.h b/xpcom/glue/nsCRTGlue.h
 index 8caa1ae2727a..d80398a794c3 100644
 --- a/xpcom/glue/nsCRTGlue.h
 +++ b/xpcom/glue/nsCRTGlue.h
 @@ -100,6 +100,11 @@ bool NS_IsLower(char aChar);

  bool NS_IsAscii(char16_t aChar);
  bool NS_IsAscii(const char16_t* aString);
 +#ifdef MOZ_USE_CHAR16_WRAPPER
 +bool NS_IsAscii(char16ptr_t aString) {
 +   return NS_IsAscii(static_cast(aString));
 +}
 +#endif
  bool NS_IsAsciiAlpha(char16_t aChar);
  bool NS_IsAsciiDigit(char16_t aChar);
  bool NS_IsAsciiWhitespace(char16_t aChar);
 }}}

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

Re: [tor-bugs] #21969 [Core Tor/Tor]: We're missing descriptors for some of our primary entry guards

[Tor Bug Tracker & Wiki]

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

Comment (by asn):

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

 Hello, can you please explain exactly what leftover state you are talking
 about? I don't see any important state that should be cleared, and hence
 I'm suggesting we defer any such thing to release 0.3.4, since 0.3.3 is
 about to get closed.

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

Re: [tor-bugs] #16849 [Core Tor/Tor]: clear_status_flags_on_sybil might want to clear more flags

[Tor Bug Tracker & Wiki]

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

 * status:  needs_revision => needs_review


Comment:

 I have a patch, I think it is a good approach :)

 I hope everything is fine, check my github
 [https://github.com/ffmancera/tor-1/tree/bug16849 ​branch bug16849.]

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25334 [Applications/Tor Mail]: Missing SearchAPI.h on Windows builds of Thunderbird when cross-compiling on Linux

[Tor Bug Tracker & Wiki]

#25334: Missing SearchAPI.h on Windows builds of Thunderbird when 
cross-compiling
on Linux
---+
 Reporter:  sukhbir|  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Applications/Tor Mail  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+

Comment (by sukhbir):

 Replying to [comment:1 boklm]:
 > Is it an issue in the x86_64 build only or does it also affect the i686
 build?

 Both. It's because the SearchAPI.h is missing in the included mingw-w64
 headers and so I am guessing the solution is to add this file to the
 mingw-w64 headers?

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

Re: [tor-bugs] #25333 [Core Tor/Tor]: NOT SECURE CONECTION please help

[Tor Bug Tracker & Wiki]

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

Comment (by Dude_Virus):

 Replying to [comment:17 cypherpunks]:
 > Replying to [comment:16 Dude_Virus]:
 > > There definitely seems to be some issue with the desktop version of
 the browser. I just installed TOR browser on a newly formatted laptop and
 it gives the same issue. But if I use Orbot and Orfox browser on my
 android phone then TOR is working. Unable to figure out what is the issue.
 > Are you using bridges on Orbot'n'Orfox? Are you using bridges on the
 desktop version?
 >
 > (I'm on a desktop but can't reproduce the issue.)


 No I am no using bridges anywhere BUT I have tried configuring bridges on
 my desktop however no luck.

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

Re: [tor-bugs] #25306 [Core Tor/Tor]: tor_assertion_failed_(): Bug: ../src/or/hs_service.c:1985: rotate_all_descriptors: Assertion service->desc_current failed; aborting.

[Tor Bug Tracker & Wiki]

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

Comment (by asn):

 Did some digging here but it's hard to figure it out without any logs :(
 Not sure how we can end up with `desc_current` being NULL there after a
 clock jump. I can think of some ways to avoid the assert, but I'd like to
 find the root cause instead of blindly applying duct-tape.

 Perhaps one way to approach this is to try to reproduce this ourselves by
 setting up an hsv3 and clock jumping. Alternatively, we can make a branch
 with some diagnostics in the case of this bugs, and wait for some useful
 logs to appear.

 In any case, due to the clock jump scenario this does not seem like a
 common urgent bug to fix, but we should try to address it soon.

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

Re: [tor-bugs] #25333 [Core Tor/Tor]: NOT SECURE CONECTION please help

[Tor Bug Tracker & Wiki]

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

Comment (by cypherpunks):

 Replying to [comment:16 Dude_Virus]:
 > There definitely seems to be some issue with the desktop version of the
 browser. I just installed TOR browser on a newly formatted laptop and it
 gives the same issue. But if I use Orbot and Orfox browser on my android
 phone then TOR is working. Unable to figure out what is the issue.
 Are you using bridges on Orbot'n'Orfox? Are you using bridges on the
 desktop version?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24759 [Core Tor/Tor]: (Sandbox) Caught a bad syscall attempt (syscall socket)

[Tor Bug Tracker & Wiki]

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

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


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

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

[Tor Bug Tracker & Wiki]

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

Comment (by nickm):

 David says:

 > I can only see this assert() being triggered if we added twice the same
 ewma circ policy to the active circuit queue.

 That reminds me of #24700 , which is fixed in 0.3.3.2-alpha, but not in
 0.3.2.9.  Could this be another case of that bug?

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

Re: [tor-bugs] #24775 [Core Tor/Tor]: Reduce "Channel padding timeout scheduled" NOTICE messages

[Tor Bug Tracker & Wiki]

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

Comment (by nickm):

 Could this be a duplicate of #22212?  If so, it's fixed in 0.3.3, and
 scheduled for backport to earlier versions once there's a little more
 testing.

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

Re: [tor-bugs] #25055 [Core Tor/Tor]: string_is_valid_hostname() returns true for IPv4 addresses

[Tor Bug Tracker & Wiki]

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

Comment (by nickm):

 {{{
size_t len = strlen(string);

 -  tor_assert(string);
 -  tor_assert(len > 0);
 +  if (string == NULL)
 +return 0;
 +
 +  len = strlen(string);
 }}}

 Looks like you're doing strlen(string) before you check it for NULL, and
 after.

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

Re: [tor-bugs] #25275 [Internal Services/Service - git]: Please delete tag collector-1.5.0 in collector.git

[Tor Bug Tracker & Wiki]

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

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


Comment:

 This is fixed now. hiro gave me more permissions, I deleted the tag, hiro
 revoked the additional permissions. Closing. 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] #25331 [Applications/Tor Browser]: Test from #18912 failing

[Tor Bug Tracker & Wiki]

#25331: Test from #18912 failing
--+---
 Reporter:  arthuredelstein   |  Owner:  tbb-team
 Type:  defect| Status:  needs_information
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---
Changes (by mcs):

 * status:  new => needs_information


Comment:

 After poking around for a while with a 8.0a1-ish build of Tor Browser,
 Kathy and I learned that the test is failing due to #18087. When we run
 the test using the command below it works (i.e., the expected error code
 is generated):
 {{{
 ./mach mochitest --setpref=security.nocertdb=false
 toolkit/mozapps/update/tests/chrome/test_0790_check_certPinning_noUpdate.xul
 }}}

 Arthur, when you ran the test on mozilla-central was `security.nocertdb`
 set to `false`? I am not sure if the build you are using has the Tor
 Browser default prefs or not.

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

Re: [tor-bugs] #25335 [Core Tor/Tor]: Tor relay node CPUWORKER failed error mssage

[Tor Bug Tracker & Wiki]

#25335: Tor relay node CPUWORKER failed error mssage
--+
 Reporter:  DarthKeizer   |  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 DarthKeizer):

 Also made a reddit
 
thread[https://www.reddit.com/r/TOR/comments/7wlesb/warn_assign_to_cpuworker_failed_ignoring_678/]

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

Re: [tor-bugs] #25333 [Core Tor/Tor]: NOT SECURE CONECTION please help

[Tor Bug Tracker & Wiki]

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

Comment (by Dude_Virus):

 There definitely seems to be some issue with the desktop version of the
 browser. I just installed TOR browser on a newly formatted laptop and it
 gives the same issue. But if I use Orbot and Orfox browser on my android
 phone then TOR is working. Unable to figure out what is the issue.

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

[tor-bugs] #25335 [Core Tor/Tor]: Tor relay node CPUWORKER failed error mssage

[Tor Bug Tracker & Wiki]

#25335: Tor relay node CPUWORKER failed error mssage
--+
 Reporter:  DarthKeizer   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 10:15:18 [WARN] assign_to_cpuworker failed. Ignoring.  [464 duplicates
 hidden]

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25334 [Applications/Tor Mail]: Missing SearchAPI.h on Windows builds of Thunderbird when cross-compiling on Linux

[Tor Bug Tracker & Wiki]

#25334: Missing SearchAPI.h on Windows builds of Thunderbird when 
cross-compiling
on Linux
---+
 Reporter:  sukhbir|  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Applications/Tor Mail  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+

Comment (by boklm):

 Is it an issue in the x86_64 build only or does it also affect the i686
 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] #25253 [Internal Services/Service - lists]: Remove Tor Weekly News from lists.torproject.org

[Tor Bug Tracker & Wiki]

#25253: Remove Tor Weekly News from lists.torproject.org
---+-
 Reporter:  steph  |  Owner:  qbi
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Internal Services/Service - lists  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+-

Comment (by steph):

 ping :)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25334 [Applications/Tor Mail]: Missing SearchAPI.h on Windows builds of Thunderbird when cross-compiling on Linux

[Tor Bug Tracker & Wiki]

#25334: Missing SearchAPI.h on Windows builds of Thunderbird when 
cross-compiling
on Linux
---+
 Reporter:  sukhbir|  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Applications/Tor Mail  |Version:
 Severity:  Normal |   Keywords:
Actual Points: |  Parent ID:
   Points: |   Reviewer:
  Sponsor: |
---+
 {{{
 31:31.93 /var/tmp/build/thunderbird-
 48f960ae7db5/mail/components/search/nsMailWinSearchHelper.cpp:17:23: fatal
 error: SearchAPI.h: No such file or directory
 31:31.93 compilation terminated.
 31:31.93
 31:31.93 In the directory  /var/tmp/build/thunderbird-48f960ae7db5/obj-
 mingw/mail/components/search
 31:31.93 The following command failed to execute properly:
 31:31.93 /var/tmp/dist/mingw-w64/helpers/x86_64-w64-mingw32-g++
 -std=gnu++11 -mwindows -o nsMailWinSearchHelper.o -c -DNDEBUG=1
 -DTRIMMED=1 -DSTATIC_EXPORTABLE_JS_API -DMOZ_HAS_MOZGLUE
 -DMOZILLA_INTERNAL_API -DIMPL_LIBXUL -I/var/tmp/build/thunderbird-
 48f960ae7db5/mail/components/search -I/var/tmp/build/thunderbird-
 48f960ae7db5/obj-mingw/mail/components/search -I/var/tmp/build
 /thunderbird-48f960ae7db5/obj-mingw/dist/include -I/var/tmp/build
 /thunderbird-48f960ae7db5/obj-mingw/dist/include/nspr -I/var/tmp/build
 /thunderbird-48f960ae7db5/obj-mingw/dist/include/nss -DMOZILLA_CLIENT
 -include /var/tmp/build/thunderbird-48f960ae7db5/obj-mingw/mozilla-
 config.h -MD -MP -MF .deps/nsMailWinSearchHelper.o.pp -Wall -Wc++11-compat
 -Wempty-body -Wignored-qualifiers -Woverloaded-virtual -Wpointer-arith
 -Wsign-compare -Wtype-limits -Wunreachable-code -Wwrite-strings -Wno-
 invalid-offsetof -Wc++14-compat -Wno-error=maybe-uninitialized -Wno-error
 =deprecated-declarations -Wno-error=array-bounds -Wno-format -fno-
 lifetime-dse -fno-exceptions -fno-strict-aliasing -mms-bitfields -fno-rtti
 -fno-exceptions -fno-math-errno -pipe -g -O -fomit-frame-pointer
 /var/tmp/build/thunderbird-
 48f960ae7db5/mail/components/search/nsMailWinSearchHelper.cpp
 }}}

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25225 [Webpages/Website]: Create redirect for the Tor Relay Guide

[Tor Bug Tracker & Wiki]

#25225: Create redirect for the Tor Relay Guide
--+-
 Reporter:  steph |  Owner:  (none)
 Type:  task  | Status:  closed
 Priority:  Very High |  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:  implemented
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+-
Changes (by steph):

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


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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: #21087, #23421, #24384, #20421, ...

[Tor Bug Tracker & Wiki]

Batch modification to #21087, #23421, #24384, #20421, #22695 by karsten:
priority to Medium

Comment:
This ticket has not been modified in the last 2 months or even longer. Setting 
priority to medium.

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

[Tor Bug Tracker & Wiki]

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

Comment (by karsten):

 Sent you that output via private mail.

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

Re: [tor-bugs] #25333 [Core Tor/Tor]: NOT SECURE CONECTION please help

[Tor Bug Tracker & Wiki]

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

Comment (by Dude_Virus):

 Replying to [comment:14 cypherpunks]:
 > Replying to [comment:12 Dude_Virus]:
 > > I suspect this issue to be with the HTTPS Everywhere plugin which is
 there along with the TOR browser.
 >
 > If it's due to HTTPS-E addon then Which specific site do you have issues
 with?

 All the sites are having issues on the OR browser. Even the torproject
 site doesnt open. Even when i do test tor network settings its just show
 connection not secured.

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

Re: [tor-bugs] #25333 [Core Tor/Tor]: NOT SECURE CONECTION please help

[Tor Bug Tracker & Wiki]

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

Comment (by cypherpunks):

 Replying to [comment:12 Dude_Virus]:
 > I suspect this issue to be with the HTTPS Everywhere plugin which is
 there along with the TOR browser.

 If it's due to HTTPS-E addon then Which specific site do you have issues
 with?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #8387 [Core Tor/Tor]: Unbuilt one-hop circuits sometimes hang around forever

[Tor Bug Tracker & Wiki]

#8387: Unbuilt one-hop circuits sometimes hang around forever
-+-
 Reporter:  mikeperry|  Owner:  nickm
 Type:  defect   | Status:  new
 Priority:  High |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-client, 2016-bug-retrospective,  |  Actual Points:
  needs-insight needs-analysis maybe-logs-   |
  would-help |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by asn):

 Got it on my hsv3 HS:
 {{{
 Feb 22 09:53:43.000 [notice] Diagnostic for issue 8387: Found 1 one-hop
 circuits more than 1800 seconds old! Logging 1...
 Feb 22 09:53:43.000 [notice]   #0 created at 2018-02-22 09:20:08. open,
 General-purpose client. Not marked for close. Package window: 1000. usable
 for new conns. Not marked dirty.
 Feb 22 09:53:43.000 [notice] It has been 23 seconds since I last called
 circuit_expire_old_circuits_clientside().
 }}}

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

Re: [tor-bugs] #25333 [Core Tor/Tor]: NOT SECURE CONECTION please help

[Tor Bug Tracker & Wiki]

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

Comment (by Dude_Virus):

 TOR connection works but then it shows the below.

 2/22/2018 11:57:38 AM.900 [NOTICE] Bootstrapped 90%: Establishing a Tor
 circuit
 2/22/2018 11:57:39 AM.700 [NOTICE] Tor has successfully opened a circuit.
 Looks like client functionality is working.
 2/22/2018 11:57:39 AM.700 [NOTICE] Bootstrapped 100%: Done
 2/22/2018 11:57:41 AM.200 [NOTICE] New control connection opened from
 127.0.0.1.
 2/22/2018 11:57:41 AM.300 [NOTICE] New control connection opened from
 127.0.0.1.
 2/22/2018 11:57:57 AM.000 [WARN] Proxy Client: unable to connect to
 169.229.59.74:31493 ("general SOCKS server failure")

 I have tried configuring a bridge obfs3 / obfs4 but no luck.

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

Re: [tor-bugs] #25333 [Core Tor/Tor]: NOT SECURE CONECTION please help

[Tor Bug Tracker & Wiki]

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

Comment (by Dude_Virus):

 I seem to be having the same issue. Any website that I try in the TOR
 browser fails to load with the message Connection Not Secure. Even cant
 check for the TOR browser update as it reports no data received.

 I suspect this issue to be with the HTTPS Everywhere plugin which is there
 along with the TOR browser.

 I have Orbot and Orfox on my phone and there the TOR works fine because
 the sites are not being forced HTTPS. I used the wifi connection which my
 desktop PC uses hence TOR is not blocked on the connection. Not sure what
 is going on.

 I have tried uninstalling TOR and reinstalling. Will try the bridges and
 report.

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

Re: [tor-bugs] #25161 [Metrics/CollecTor]: Fix any memory problem caused by number of log files to be imported by the webstats module

[Tor Bug Tracker & Wiki]

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

Comment (by iwakeh):

 Yes, #25317 is the focus.  Could you just provide output from (please edit
 the log path, if necessary)
 {{{
 grep -hi "processing " logs/collector-all.*
 }}}

 for the latest run?
 That would point out which hosts were processed fine and how many there
 were and which led to the final exception.

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

Re: [tor-bugs] #25112 [Applications/Tor Browser]: Tor Browser 7.5 is not working on Windows Vista 64bit

[Tor Bug Tracker & Wiki]

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

 * cc: tbb-team (added)


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

Re: [tor-bugs] #25161 [Metrics/CollecTor]: Fix any memory problem caused by number of log files to be imported by the webstats module

[Tor Bug Tracker & Wiki]

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

Comment (by karsten):

 Hmm, I can't send you the logs easily, because there are so many of them.
 And I think i pasted the most useful parts above anyway.

 I did not process real logs. I processed all previously sanitized logs
 except for `dist.torproject.org` logs. The log message/exception above
 looks like a result of running out of memory, not of the request line
 being ill-formed.

 But really, I think focusing on #25317 for now makes more sense. Happy to
 provide more details from the next test. Hope that's okay!

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

Re: [tor-bugs] #25333 [Core Tor/Tor]: NOT SECURE CONECTION please help

[Tor Bug Tracker & Wiki]

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

Comment (by teor):

 Have you tried using bridges?
 Try these instructions:
 https://www.torproject.org/docs/bridges#AddTorNotWorks

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

Re: [tor-bugs] #25161 [Metrics/CollecTor]: Fix any memory problem caused by number of log files to be imported by the webstats module

[Tor Bug Tracker & Wiki]

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

Comment (by iwakeh):

 I assume you are processing real logs?  Otherwise the line `DEBUG
 o.t.d.l.WebServerAccessLogLine:143 Unmatchable line ...` shouldn't appear.

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

Re: [tor-bugs] #25161 [Metrics/CollecTor]: Fix any memory problem caused by number of log files to be imported by the webstats module

[Tor Bug Tracker & Wiki]

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

Comment (by iwakeh):

 True, let's wait for #25317, but would it be possible to make the log
 available to me?
 'm particularly interested to see which hosts were processed before the
 OOM.
 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] #25333 [Core Tor/Tor]: NOT SECURE CONECTION please help

[Tor Bug Tracker & Wiki]

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

Comment (by cypherpunks):

 Replying to [comment:7 kiokawasaki1998]:
 > browser writes  secure conection failed
 Does that happen on every single webpage that you're trying to access?
 Also are you on a network that tries to block Tor?

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

Re: [tor-bugs] #25161 [Metrics/CollecTor]: Fix any memory problem caused by number of log files to be imported by the webstats module

[Tor Bug Tracker & Wiki]

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

Comment (by karsten):

 So, after moving all log files for virtual host `dist.torproject.org` out
 of the way, I ran the following bulk import:

 {{{
 2018-02-21 19:41:30,021 INFO o.t.c.c.CollecTorMain:66 Starting webstats
 module of CollecTor.
 [...]
 2018-02-21 23:01:54,276 DEBUG o.t.d.l.WebServerAccessLogLine:143
 Unmatchable line: '[scrubbed by karsten]'.
 java.lang.OutOfMemoryError: GC overhead limit exceeded
 at java.util.HashMap.newNode(HashMap.java:1747)
 at java.util.HashMap.putVal(HashMap.java:642)
 at java.util.HashMap.put(HashMap.java:612)
 at
 
java.time.format.DateTimeParseContext.setParsedField(DateTimeParseContext.java:365)
 at
 
java.time.format.DateTimeFormatterBuilder$OffsetIdPrinterParser.parse(DateTimeFormatterBuilder.java:3381)
 at
 
java.time.format.DateTimeFormatterBuilder$CompositePrinterParser.parse(DateTimeFormatterBuilder.java:2208)
 at
 
java.time.format.DateTimeFormatter.parseUnresolved0(DateTimeFormatter.java:2010)
 at
 java.time.format.DateTimeFormatter.parseResolved0(DateTimeFormatter.java:1939)
 at
 java.time.format.DateTimeFormatter.parse(DateTimeFormatter.java:1851)
 at java.time.ZonedDateTime.parse(ZonedDateTime.java:597)
 at
 
org.torproject.descriptor.log.WebServerAccessLogLine.makeLine(WebServerAccessLogLine.java:129)
 at
 
org.torproject.collector.webstats.SanitizeWeblogs.lambda$lineStream$7(SanitizeWeblogs.java:192)
 at
 
org.torproject.collector.webstats.SanitizeWeblogs$$Lambda$34/783273584.apply(Unknown
 Source)
 at
 java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)
 at java.util.Iterator.forEachRemaining(Iterator.java:116)
 at
 
java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801)
 at
 java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
 at
 java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
 at
 java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708)
 at
 java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
 at
 java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:499)
 at
 
org.torproject.collector.webstats.SanitizeWeblogs.lineStream(SanitizeWeblogs.java:193)
 at
 
org.torproject.collector.webstats.SanitizeWeblogs.lambda$findCleanWrite$1(SanitizeWeblogs.java:111)
 at
 
org.torproject.collector.webstats.SanitizeWeblogs$$Lambda$15/1716312251.apply(Unknown
 Source)
 at
 java.util.stream.ReferencePipeline$7$1.accept(ReferencePipeline.java:267)
 at
 java.util.TreeMap$ValueSpliterator.forEachRemaining(TreeMap.java:2897)
 at
 java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
 at
 java.util.stream.ForEachOps$ForEachTask.compute(ForEachOps.java:291)
 at
 java.util.concurrent.CountedCompleter.exec(CountedCompleter.java:731)
 at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289)
 at
 java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1056)
 at
 java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1692)
 }}}

 I screwed up the `top` command and monitored an earlier process ID that
 was long gone when I started this run, so I can't say anything about
 memory usage. But it looks like we did run out of memory there.

 I'd say let's wait for #25317 and then try again with all logs. It might
 have an impact.

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

Re: [tor-bugs] #25112 [Applications/Tor Browser]: Tor Browser 7.5 is not working on Windows Vista 64bit

[Tor Bug Tracker & Wiki]

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

 * status:  needs_information => assigned


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

Re: [tor-bugs] #25112 [Applications/Tor Browser]: Tor Browser 7.5 is not working on Windows Vista 64bit

[Tor Bug Tracker & Wiki]

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

Comment (by gk):

 So, FWIW, we are hitting essentially
 https://bugzilla.mozilla.org/show_bug.cgi?id=1110760.

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