Re: [tor-dev] [tor-talk] Tor Research Framework update

2014-09-12 Thread Tim
On 13 Sep 2014, at 06:19 , George Kadianakis wrote: > Tim writes: > >> On 13 Aug 2014, at 22:33 , George Kadianakis wrote: >> >>> My plan was to make a Peach fuzzer to achieve this [0], but as I >>> mentioned in a previous email I never got past the V3 link handshake >>> since I actually had

Re: [tor-dev] [tor-talk] Tor Research Framework update

2014-09-12 Thread George Kadianakis
Tim writes: > On 13 Aug 2014, at 22:33 , George Kadianakis wrote: > >> My plan was to make a Peach fuzzer to achieve this [0], but as I >> mentioned in a previous email I never got past the V3 link handshake >> since I actually had to implement Tor's crypto to get past. >> >> Someone would need

Re: [tor-dev] [tor-talk] Tor Research Framework update

2014-08-14 Thread str4d
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 08/14/2014 08:14 AM, George Kadianakis wrote: > Tim writes: > >> On 13 Aug 2014, at 22:33 , George Kadianakis >> wrote: >> >>> My plan was to make a Peach fuzzer to achieve this [0], but as >>> I mentioned in a previous email I never got past

Re: [tor-dev] [tor-talk] Tor Research Framework update

2014-08-14 Thread George Kadianakis
Tim writes: > On 13 Aug 2014, at 22:33 , George Kadianakis wrote: > >> My plan was to make a Peach fuzzer to achieve this [0], but as I >> mentioned in a previous email I never got past the V3 link handshake >> since I actually had to implement Tor's crypto to get past. >> >> Someone would need

Re: [tor-dev] [tor-talk] Tor Research Framework update

2014-08-13 Thread Tim
On 13 Aug 2014, at 22:33 , George Kadianakis wrote: > My plan was to make a Peach fuzzer to achieve this [0], but as I > mentioned in a previous email I never got past the V3 link handshake > since I actually had to implement Tor's crypto to get past. > > Someone would need to implement all this

Re: [tor-dev] [tor-talk] Tor Research Framework update

2014-08-13 Thread George Kadianakis
Tim writes: >> On 13 Aug 2014, at 0:10, George Kadianakis wrote: >> >> Gareth Owen writes: > ... >>> The framework implements the tor protocol so should be easy to modify to do >>> fuzzing of the actual protocol but I'm skeptical how successful this would >>> be, I can only think of a couple o

Re: [tor-dev] [tor-talk] Tor Research Framework update

2014-08-13 Thread Tim
> On 13 Aug 2014, at 0:10, George Kadianakis wrote: > > Gareth Owen writes: ... >> The framework implements the tor protocol so should be easy to modify to do >> fuzzing of the actual protocol but I'm skeptical how successful this would >> be, I can only think of a couple of places that could be

Re: [tor-dev] [tor-talk] Tor Research Framework update

2014-08-12 Thread George Kadianakis
Gareth Owen writes: > Hi George > > Thanks for your reply and information+links. Tim (cc-ed) is leading the > work on the fuzzer and is looking at a couple of different frameworks. > I've set up a example that can do port-forwarding to a BEGIN_DIR service > - so you can just point a fuzzer at

Re: [tor-dev] [tor-talk] Tor Research Framework update

2014-08-11 Thread Tim
Hi George, I'm still trying to work out exactly how to go about fuzzing Tor. So far, I've been to defined an initial problem space, configured a test environment, and explored some fuzzing libraries / tools. Fuzzing Problem Space We started by looking at fuzzing Tor directory download requests

Re: [tor-dev] [tor-talk] Tor Research Framework update

2014-08-11 Thread Gareth Owen
Hi George Thanks for your reply and information+links. Tim (cc-ed) is leading the work on the fuzzer and is looking at a couple of different frameworks. I've set up a example that can do port-forwarding to a BEGIN_DIR service - so you can just point a fuzzer at the local port - this opens up a

Re: [tor-dev] [tor-talk] Tor Research Framework update

2014-08-11 Thread George Kadianakis
Gareth Owen writes: > Hi all > > I thought I'd give you an update on where the Tor Research Framework is now > at as there's been lots of development over the last few weeks. At present, > the framework is a largely fully functional tor client with code that is > easy to read, follow and cruciall