Opened 10 years ago

Last modified 7 years ago

#905 closed defect (Fixed)

ServerDNSRandomizeCase config option without effect

Reported by: Falo Owned by: nickm
Priority: Low Milestone: 0.2.1.11-alpha
Component: Core Tor/Tor Version: 0.2.1.9-alpha
Severity: Keywords:
Cc: Falo, nickm, arma Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

My Tor exit gw always randomizes cases in dns queries. Setting "ServerDNSRandomizeCase 0" has no effect. I checked with
v0.2.1.8-alpha (r17523) and v0.2.1.10-alpha (r17969).

[Automatically added by flyspray2trac: Operating System: All]

Child Tickets

Change History (16)

comment:1 Changed 10 years ago by arma

dns.c: evdns_set_option("randomize-case", "1", DNS_OPTIONS_ALL);
dns.c: evdns_set_option("randomize-case", "0", DNS_OPTIONS_ALL);
dns.c: evdns_set_option("max-timeouts:", "16", DNS_OPTIONS_ALL);
dns.c: evdns_set_option("timeout:", "10", DNS_OPTIONS_ALL);

two of these are missing colons, and the other two aren't. There's the bug perhaps.

comment:2 Changed 10 years ago by nickm

Yup. Fixing.

comment:3 Changed 10 years ago by nickm

May be fixed in r18063.

comment:4 Changed 10 years ago by nickm

Seems fixed. Reopen if it happens again?

comment:5 Changed 10 years ago by nickm

Reopened by user request. You tried r18063 and it didn't work?

comment:6 Changed 10 years ago by Falo

I just reopened this case cause it now appears to be broken the other
way round. Cases now never are randomized. Neither omitting the
config option nor setting "ServerDNSRandomizeCase 1" works.

comment:7 Changed 10 years ago by nickm

What version exactly are you running?

comment:8 Changed 10 years ago by nickm

(Also, what are you doing to check for case randomization? According to tcpdump, ServerDNSRandomizeCase 1 is working
for me with trunk.)

comment:9 Changed 10 years ago by Falo

what I said 10 minutes ago hasn't been quite correct. The config option ServerDNSRandomizeCase works as expected when tor initially reads the config file during startup. But it appears to be ignored when reloading the config by SIGHUP. In this case changing the value of ServerDNSRandomizeCase has no effect.

That's what I did some minutes ago. I rather reloaded the config by SIGHUP than killing the tor process.

comment:10 Changed 10 years ago by Falo

@Nick: yes I use tcpdump, too.
Pls check if toggling ServerDNSRandomizeCase and reloading config by kill -1 works with trunk.

comment:11 Changed 10 years ago by nickm

Is trunk better for you now?

comment:12 Changed 10 years ago by Falo

I'll try to check on Saturday. Being away on a business trip for two days.

comment:13 Changed 10 years ago by Falo

yes, trunk r18353 works perfectly for me. ServerDNSRandomizeCase now can be toggled by SIGHUP.

comment:14 Changed 10 years ago by arma

Great! Closing.

comment:15 Changed 10 years ago by arma

flyspray2trac: bug closed.

comment:16 Changed 7 years ago by nickm

Component: Tor RelayTor
Note: See TracTickets for help on using tickets.