[tor-relays] interesting tor platform string or tor bug?
nusenu at openmailbox.org
Fri Jul 8 08:30:00 UTC 2016
>> We plan on authorities rejecting descriptors with non-ASCII
>> characters in 0.2.9, if we get it implemented before the code
>> freeze. https://trac.torproject.org/projects/tor/ticket/18938
Glad to hear that.
> Hmm, I can't find an actual descriptor with these characters in it.
> The latest descriptor I can find for this relay has a normal platform
> Could this be a bug in Atlas?
I ruled that out by lookup up the descriptor.
It took me a while to find that descriptor on collector that is why I
linked it in my last email:
>>> descriptor containing that platform string:
@type server-descriptor 1.0
router inaTor 220.127.116.11 9001 0 0
-----BEGIN ED25519 CERT-----
-----END ED25519 CERT-----
protocols Link 1 2 Circuit 1
published 2016-07-07 05:50:30
fingerprint 21E8 4B29 4794 821E 2898 E8ED 1840 2E45 E4FC 351E
bandwidth 1048576 1048576 52224
note: the timestamps 07-06 vs 07-06 (relevant descriptor never ended up
in a consensus entry, last seen vs. last restarted)
> Actually, I should probably say that there are *other* descriptors
> from inaTor, which say
> platform Tor 0.2.7.6 on Windows 8
> i.e. a totally normal platform string.
> So it looks like a Tor bug -- and a memory corruption one at that.
Yes, both relays on that IP (same ORPort), changed from "Tor 0.2.7.6 on
Windows 8" to that non-ASCII string (that is why I knew he is probably
running Windows 8).
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 801 bytes
Desc: OpenPGP digital signature
More information about the tor-relays