Hi!
We're currently on track to get a stable release out on the planned
release date (August 15), which would be seriously impressive for us.
To do this, we'll need to get a release candidate out by late July.
And in order to do _that_, we'll need to prioritize the remaining
0.4.1.x tickets.
Her
> I modified exitmap to print the entire response in case the ATYP field is set
> to 04 (meaning the
> response contains an IPv6 address) but
> the response is not any longer and contains only the first 4 bytes of the
> IPv6 address.
>
> Running tor 0.3.5.8.
>
> Has this bug been fixed in late
> Running tor 0.3.5.8.
>
> Has this bug been fixed in later versions of tor or current master?
moved to trac:
https://trac.torproject.org/projects/tor/ticket/31115
--
https://twitter.com/nusenu_
https://mastodon.social/@nusenu
signature.asc
Description: OpenPGP digital signature
Thanks this is very useful information.
>>> # Tor defines a new command value, \x0f, that is used for
>> domain
>>> # resolution.
>>>
>>> self._send_all("\x05\xf0\x00\x03%s%s%s" % (chr(domain_len),
>>> domain, "\x00\x00"))
>
> Exitmap uses the SOCKS 5, resolve, DNS command: See page 4 of
> http
On July 9, 2019 8:55:00 AM UTC, nusenu wrote:
>Hi,
>
>I noticed some unexpected answers in exitmap's [1] dnsenum results
>and suspected that this has todo with IPv4 vs. IPv6.
>
>First I looked at [2] and found that it only lists IPv4 and hostnames
>as possible answers but then I realized that ex
Hi,
I noticed some unexpected answers in exitmap's [1] dnsenum results
and suspected that this has todo with IPv4 vs. IPv6.
First I looked at [2] and found that it only lists IPv4 and hostnames
as possible answers but then I realized that exitmap might not be using
the RESOLVE command?
> def
