Extend HTTP fuzzer so it fuzzes the GET handler functions

I have a draft branch for this, I'm going to fuzz with it for a while to make sure there are no show-stoppers.

I'm also curious to see if it finds #21471 (moved) in an unfixed codebase.

changed milestone to %Tor: unspecified

added component::core tor/tor fuzz milestone::Tor: unspecified points::1 priority::medium severity::normal status::new triaged-out-20170308 type::enhancement labels

I should also add the '-x' option to the instructions, like:

../afl/afl-fuzz -i ../fuzzing-corpora/http -o ../fuzzing-corpora/http_findings -x src/test/fuzz/dict/http -m none -- src/test/fuzz/fuzz-http

dgoulet
right in the case of that bug it has to be a valid base64 string decoding to 32 bytes
to hit the "ret == 0"
teor
oh wow, ok
perhaps I need to add an example request to the inputs then
or add more tokens to the dictionary

I also need to MOCK dirserv_have_any_microdesc() and similar to return 0, otherwise they crash when trying to find the data directory.

(There appears to be some code reordering here: the tor_assert() on the data directory is not triggered, but the strlen() on it fails with a NULL pointer error.)

Trac:
Component: Core Tor to Core Tor/Tor

Deferring all 0.3.1 tickets with status == new, owner == nobody, sponsor == nobody, points > 0.5, and priority < high.

I'd still take patches for most of these -- there's just nobody currently lined up to work on them in this timeframe.

Trac:
Keywords: N/A deleted, triaged-out-20170308 added
Milestone: Tor: 0.3.1.x-final to Tor: unspecified

Trac:
Status: new to assigned
Owner: N/A to teor

Disowning tickets I don't intend to work on in the next 6 months.

Trac:
Owner: teor to N/A

Mark all tickets that are assigned to nobody as "new".

Trac:
Status: assigned to new

changed time estimate to 8h

mentioned in issue #21478 (moved)

mentioned in issue #21509 (moved)

moved to tpo/core/tor#21476 (closed)

mentioned in issue tpo/core/tor#21478 (closed)

mentioned in issue tpo/core/tor#21509 (closed)