8 Commits

Author	SHA1	Message	Date
Max Moroz	0a5405683e	[tor] Fix configure flags being used in build.sh.	2017-11-01 11:42:14 -07:00
Max Moroz	a66795291a	[tor] Disable FORTIFY_SOURCE in order to let sanitizer interceptors work (#940).	2017-11-01 10:23:38 -07:00
Max Moroz	0a2bd75093	[tor] Instrument dependencies and enable MSan.	2017-10-31 14:57:44 -07:00
Abhishek Arya	2d5e2ef84f	Fix Tor build with non-existent seed corpus for some fuzzers (#469). (#481)	2017-03-26 19:26:59 -07:00
Nick Mathewson	63b3d797e0	Tor build.sh: Disable memory sentinels when fuzzing (#464) ... Tor has a few safety features that try to prevent bugs by using memory more safely. For example, by default, we terminate our IO buffers with 0-valued bytes, so that accidental string operations can't run off the end. For another example, we do some of our allocation in "memory areas" -- an obstack-style allocation in which all objects are freed at once. These features prevent a fairly large category of crash bugs, but they also prevent asan from seeing our mistakes. But when we're fuzzing, we'd like to expose as many of our mistakes as possible. With that in mind, we've added a --disable-memory-sentinels configuration option to turn off a lot of these safety features when we're fuzzing. This feature turns it on for oss-fuzz.	2017-03-16 12:46:07 -07:00
Mike Aizatsky	6f23387fa8	[tor] static linking of libraries ... @nmathewson	2017-01-10 15:09:29 -08:00
Nick Mathewson	3d351a0883	Build tor fuzzing binaries with static libevent linkage (#267) ... * Remove true && true &&... Don't ask. * Link libevent statically in tor build.sh	2017-01-10 12:32:01 -08:00
Nick Mathewson	11985a0665	Tor oss fuzzing configuration (#265) ... * Initial attempts at getting Tor to build in oss-fuzz docker. * add automake/autoconf * More work * more fixes for tor * copyright notice, corpora. * zip correctly.	2017-01-09 11:32:36 -08:00