Nick Mathewson a757f76967 Withstand failures in CLOCK_MONOTONIC_COARSE ... This came up on #21035, where somebody tried to build on a linux system with kernel headers including CLOCK_MONOTONIC_COARSE, then run on a kernel that didn't support it. I've adopted a belt-and-suspenders approach here: we detect failures at initialization time, and we also detect (loudly) failures later on. Fixes bug 21035; bugfix on 0.2.9.1-alpha when we started using monotonic time.		2016-12-21 08:17:26 -05:00
..
common	Withstand failures in CLOCK_MONOTONIC_COARSE	2016-12-21 08:17:26 -05:00
config	Merge branch 'maint-0.2.8' into maint-0.2.9	2016-12-09 08:34:24 -05:00
ext	Fix a new compilation warning with broken-mulodi i386 clang builds. :(	2016-10-11 10:29:43 -04:00
or	Merge branch 'maint-0.2.8' into maint-0.2.9	2016-12-19 07:58:43 -05:00
test	test: fix memory leak in single onion poisoning	2016-12-09 12:59:40 -05:00
tools	Merge branch 'maint-0.2.8' into maint-0.2.9	2016-11-03 15:41:04 -04:00
trunnel	Re-run trunnel.	2016-07-28 10:52:43 -04:00
win32	Bump to 0.2.9.8-dev	2016-12-19 10:13:01 -05:00
include.am	Use trunnel for crypto_pwbox encoding/decoding.	2014-09-25 11:58:14 -04:00