[tor-relays] Testing Golang relay implementation

[teor]

> On 26 Oct 2017, at 18:07, Karsten Loesing <karsten at torproject.org> wrote:
> 
> On 2017-10-26 00:09, teor wrote:
>> On 26 Oct 2017, at 06:58, Michael McLoughlin <mmcloughlin at gmail.com
>> <mailto:mmcloughlin at gmail.com>> wrote:
>>> I can easily change the descriptor if necessary?
>> 
>> As long as it conforms to the spec, it's fine.
> 
> Agreed. FWIW, the descriptor published by this relay confused Metrics
> quite a bit. But that's okay, we'll just make Metrics more robust. The
> good news is that we didn't lose any data in the process.
> 
>> We should really fuzz descriptor parsers better.
>> But that's not an appropriate thing to do on the live network, and some
>> parser code only runs on descriptors on the live network.
> 
> If somebody wants to generate a bunch of fuzzed descriptors that conform
> to the spec, I'll happily throw them into a local Metrics instance to
> see if anything else breaks. I could imagine that Damian would do the
> same with stem and Philipp with zoossh.

leekspin and maybe stem can produce valid, randomised descriptors.

Tor also has a collection of valid and invalid directory documents in:

https://gitweb.torproject.org/fuzzing-corpora.git/tree/

I'm not sure if there are any others.

--
Tim / teor

PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B
ricochet:ekmygaiu4rzgsk6n
------------------------------------------------------------------------

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20171026/a761a772/attachment.sig>