Opened 2 years ago

Closed 19 months ago

#23785 closed task (user disappeared)

[HELP!] 7.5a5's(IIRC) Tor cause DNS disruption!

Reported by: cypherpunks Owned by:
Priority: Medium Milestone: Tor: 0.3.3.x-final
Component: Core Tor/Tor Version:
Severity: Critical Keywords: 033-triage-20180320, 033-removed-20180320
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

  1. Download CURRENT latest ALPHA version of Tor Browser[1]
  2. Copy Tor executable folder to your system[2], overwrite them.
  3. Start Tor as usual, from services.msc.
  4. Query/Browse some websites.
  5. Suddenly, Tor failed to resolve any domain names!! This is critical!
  1. Download current STABLE version of Tor.
  2. Stop Tor daemon and overwrite with stable files.
  3. Start Tor. Now Tor successfully query any domains as normal.

A part of my Torrc:
"DNSPort ...."

TL;DR
I am using Tor as SOCKS proxy and DNS resolver(DNSPort).
Latest Tor, which incuded in current alpha, caused a problem.
Please fix it.

[1] I did this because I want to test v3 onions.
[2] I already have Tor daemon on this PC.

Child Tickets

Change History (8)

comment:1 Changed 2 years ago by cypherpunks

Problematic tor.exe SHA1 = d1de79200dbcbd095b551997973500ff9937b7ee

nslookup nsa.gov

can't find nsa.gov: Non-existent domain

Tor log:
I have a exact "info" level log. Where can I send it to? I don't want to post it because
this log may contain targetable information.

comment:2 Changed 2 years ago by cypherpunks

mildly related?

[warn] tor_bug_occurred_(): Bug: scheduler_kist.c:520: kist_scheduler_schedule: Non-fatal assertion !((diff < 0)) failed. (Future instances of this warning will be silenced.) (on Tor 0.3.2.1-alpha )
[warn] Bug: Non-fatal assertion !((diff < 0)) failed in kist_scheduler_schedule at scheduler_kist.c:520. (Stack trace not available) (on Tor 0.3.2.1-alpha )

comment:3 Changed 2 years ago by cypherpunks

Status: newneeds_information

No, it's not related to those bugs, and you can remove "targetable information" from your log and then post it here so that we can see which specific error causes this here. Thanks.

comment:4 Changed 2 years ago by nickm

Milestone: Tor: 0.3.2.x-final
Priority: Very HighHigh

Can you identify the last version that works for you, and the first version that breaks? It would also be helpful to see what is in your logs around when the warning occurs, as cypherpunks notes above.

For what it's worth: DNS lookup over DNSPort works for me with the current alpha, so it's not trivial to track this down.

comment:5 Changed 2 years ago by nickm

Milestone: Tor: 0.3.2.x-finalTor: 0.3.3.x-final
Priority: HighMedium

Hi! Are you still having this problem? Do you think you could answer the questions above?

comment:6 Changed 19 months ago by nickm

Keywords: 033-triage-20180320 added

Marking all tickets reached by current round of 033 triage.

comment:7 Changed 19 months ago by nickm

Keywords: 033-removed-20180320 added

Mark all not-already-included tickets as pending review for removal from 0.3.3 milestone.

comment:8 Changed 19 months ago by isis

Resolution: user disappeared
Status: needs_informationclosed
Note: See TracTickets for help on using tickets.