[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [tor-talk] DNS hijacking
If s/he is using Tor and hasn't done something odd to reconfigure, then
the DNS resolve is done at the exit relay. His local DNS resolver is
never contacted. Also, original poster said that local resolution
worked correctly (presumably the correct IP address is known); only
over Tor was there a problem.
On Fri, Apr 03, 2015 at 07:32:05PM -0400, Max Bond wrote:
> Have you tried this over multiple circuits? Is it possible your DNS
> provider is the one doing something naughty?
> On Fri, Apr 3, 2015 at 7:12 PM, grarpamp <email@example.com> wrote:
> > On Fri, Apr 3, 2015 at 6:30 PM, Justaguy <firstname.lastname@example.org> wrote:
> > > If you could find out the exit, that is doing this, you can report them,
> > > to https://trac.torproject.org/projects/tor/wiki/doc/ReportingBadRelays
> > Most users will not be able to figure this out because until
> > this ticket is implemented there is no simple way to do so.
> > Without being able to at least issue a simple getevents for
> > the backbuffer in the moment, Tor is likely to have subsequently
> > switched exits, the user will have nothing to go on, and have
> > given up inquiry. So we end up missing badexits without this.
> > Combine setevents circ and stream
> > https://trac.torproject.org/projects/tor/ticket/11179
> > --
> > tor-talk mailing list - email@example.com
> > To unsubscribe or change other settings go to
> > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
> tor-talk mailing list - firstname.lastname@example.org
> To unsubscribe or change other settings go to
tor-talk mailing list - email@example.com
To unsubscribe or change other settings go to