Tor resolves invalid .onion addresses when AutomapHostsOnResolve is 1.

If AutomapHostsOnResolve 1 is set, Tor will resolve invalid .onion addresses to local addresses.

Trac:
Username: katmagic

changed milestone to %Tor: unspecified

added component::core tor/tor dns milestone::Tor: unspecified onions priority::low reporter::katmagic resolution::wontfix severity::normal status::closed tor-client type::defect labels

Invalid in the sense of being too short, or containing invalid characters? Sounds like a possible bug, though I wonder whether in the name of consistency we want to go down this route. After all, for no other cases does AutomapHostsOnResolve try to ensure that the address is well formed.

Trac:
Priority: normal to minor
Milestone: N/A to Tor: 0.2.3.x-final

Trac:
Milestone: Tor: 0.2.3.x-final to Tor: unspecified

Trac:
Keywords: onions dns deleted, onions dns tor-client added

Trac:
Component: Tor Client to Tor

Worth looking at during 0.2.7 triage IMO

Trac:
Milestone: Tor: unspecified to Tor: 0.2.7.x-final

Trac:
Status: new to assigned

Marking triaged-out items from first round of 0.2.7 triage.

Trac:
Keywords: onions dns tor-client deleted, dns, 027-triaged-1-out, onions, tor-client added

Make all non-needs_review, non-needs_revision, 027-triaged-1-out items belong to 0.2.???

Trac:
Milestone: Tor: 0.2.7.x-final to Tor: 0.2.???

Milestone renamed

Trac:
Milestone: Tor: 0.2.??? to Tor: 0.3.???

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

Trac:
Keywords: N/A deleted, tor-03-unspecified-201612 added
Milestone: Tor: 0.3.??? to Tor: unspecified

Remove an old triaging keyword.

Trac:
Keywords: tor-03-unspecified-201612 deleted, N/A added

Trac:
Keywords: N/A deleted, 027-triaged-in added

Trac:
Keywords: 027-triaged-in deleted, N/A added

Trac:
Keywords: 027-triaged-1-out deleted, N/A added

Change the status of all assigned/accepted Tor tickets with owner="" to "new".

Trac:
Status: assigned to new

After all, for no other cases does AutomapHostsOnResolve try to ensure that the address is well formed.

I think that's still convincing to me: AutomapHostsOnResolve shouldn't do validation. Let's reopen this if we learn some reason it should.

Trac:
Severity: N/A to Normal
Sponsor: N/A to N/A
Status: new to closed
Resolution: N/A to wontfix
Reviewer: N/A to N/A

closed

moved to tpo/core/tor#4699 (closed)