summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2016-12-19Remove a blank linetor-0.2.8.12Nick Mathewson
2016-12-190.2.8.12 releasenotesNick Mathewson
2016-12-19Merge branch 'maint-0.2.8' into release-0.2.8Nick Mathewson
2016-12-19Bump to 0.2.8.12Nick Mathewson
2016-12-19Merge branch 'maint-0.2.8' into release-0.2.8Nick Mathewson
2016-12-19start an 0.2.8.12 blurbNick Mathewson
2016-12-19Merge branch 'bug21018_024' into maint-0.2.8Nick Mathewson
2016-12-19Merge branch 'maint-0.2.8' into release-0.2.8Nick Mathewson
2016-12-19Merge remote-tracking branch 'teor/new-fallbacks-028-20161219' into maint-0.2.8Nick Mathewson
2016-12-19Update the fallback directory mirror list in December 2016teor
Replace the 81 remaining fallbacks of the 100 originally introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177 fallbacks (123 new, 54 existing, 27 removed) generated in December 2016. Resolves ticket 20170.
2016-12-18Make log message warn about detected attempts to exploit 21018.Nick Mathewson
2016-12-18Fix parsing bug with unecognized token at EOSNick Mathewson
In get_token(), we could read one byte past the end of the region. This is only a big problem in the case where the region itself is (a) potentially hostile, and (b) not explicitly nul-terminated. This patch fixes the underlying bug, and also makes sure that the one remaining case of not-NUL-terminated potentially hostile data gets NUL-terminated. Fix for bug 21018, TROVE-2016-12-002, and CVE-2016-1254
2016-12-09Merge branch 'maint-0.2.8' into release-0.2.8Nick Mathewson
2016-12-09Merge branch 'maint-0.2.7' into maint-0.2.8Nick Mathewson
2016-12-09Merge branch 'maint-0.2.6' into maint-0.2.7Nick Mathewson
2016-12-09Merge branch 'maint-0.2.5' into maint-0.2.6Nick Mathewson
2016-12-09Merge branch 'maint-0.2.4' into maint-0.2.5Nick Mathewson
2016-12-09Update geoip and geoip6 to the December 7 2016 database.Karsten Loesing
2016-12-08Merge branch 'maint-0.2.8' into release-0.2.8Nick Mathewson
2016-12-08Bump to 0.2.8.11-devNick Mathewson
2016-12-08Merge branch 'maint-0.2.8' into release-0.2.8tor-0.2.8.11Nick Mathewson
2016-12-08Merge remote-tracking branch 'origin/maint-0.2.8' into maint-0.2.8Nick Mathewson
2016-12-08Copy ChangeLog into ReleaseNotes; pick a date (today)Nick Mathewson
2016-12-08Merge branch 'maint-0.2.8' into release-0.2.8Nick Mathewson
2016-12-08Bump to 0.2.8.11Nick Mathewson
2016-12-07Mention the 2nd part of 20865 in the changelogNick Mathewson
2016-12-07Merge branch 'maint-0.2.8' into release-0.2.8Nick Mathewson
2016-12-07Actually include the changelog though.Nick Mathewson
2016-12-07Backport the other sierra fix in 20865.Nick Mathewson
They added clock_gettime(), but with tv_nsec as a long, whereas tv_usec is a __darwin_suseconds_t (a.k.a. 'int'). Now, why would they do that? Are they preparing for a world where there are more than 2 billion nanoseconds per second? Are they planning for having int be less than 32 bits again? Or are they just not paying attention to the Darwin API? Also, they forgot to mark clock_gettime() as Sierra-only, so even if we fixed the issue here, we'd still be stick with portability breakage like we were for 0.2.9. So, just disable clock_gettime() on apple.
2016-12-07Start a changelog for 0.2.8.11Nick Mathewson
2016-12-05Merge branch 'maint-0.2.8' into release-0.2.8Nick Mathewson
2016-12-05Merge branch 'getentropy_028' into maint-0.2.8Nick Mathewson
2016-12-0520865: Don't use getentropy() on OSX Sierra.Nick Mathewson
Tor 0.2.9 has a broader range of fixes and workarounds here, but for 0.2.8, we're just going to maintain the existing behavior. (The alternative would be to backport both 1eba088054eca1555b455ee4a2adfafecb888af9 and 16fcbd21c963a9a65bf55024680c8323c8b7175d , but the latter is kind of a subtle kludge in the configure.ac script, and I'm not a fan of backporting that kind of thing.)
2016-12-05Merge branch 'maint-0.2.8' into release-0.2.8Nick Mathewson
2016-12-05Always Use EVP_aes_*_ctr() with openssl 1.1Nick Mathewson
(OpenSSL 1.1 makes EVP_CIPHER_CTX opaque, _and_ adds acceleration for counter mode on more architectures. So it won't work if we try the older approach, and it might help if we try the newer one.) Fixes bug 20588.
2016-12-02Merge branch 'maint-0.2.8' into release-0.2.8Nick Mathewson
2016-12-02Bump to 0.2.8.10-devNick Mathewson
2016-12-02put the 0.2.8.10 changelog in the releasenotes tootor-0.2.8.10Roger Dingledine
2016-12-02fix typoRoger Dingledine
also reorder a stanza to put the more exciting bug first
2016-12-02Pick a release date.Nick Mathewson
2016-12-01Merge branch 'maint-0.2.8' into release-0.2.8Nick Mathewson
2016-12-01Bump to 0.2.8.10Nick Mathewson
2016-12-01Start an 0.2.8.10 changelogNick Mathewson
All entries are copied verbatim from the 029 changelog.
2016-12-01Merge branch 'maint-0.2.8' into release-0.2.8Nick Mathewson
2016-11-22Try to work around breakage in the OSX 10.12 SDK.Nick Mathewson
Apple is supposed to decorate their function declarations with macros to indicate which OSX version introduced them, so that you can tell the compiler that you want to build against certain versions of OSX. But they forgot to do that for clock_gettime() and getentropy(), both of which they introduced in 10.12. This patch adds a kludge to the configure.ac script where, if we detect that we are targeting OSX 10.11 or earlier, we don't even probe to see if the two offending functions are present. Closes ticket 20235.
2016-11-07Merge branch 'maint-0.2.8' into release-0.2.8Nick Mathewson
2016-11-07Merge branch 'maint-0.2.7' into maint-0.2.8Nick Mathewson
2016-11-07Merge branch 'maint-0.2.6' into maint-0.2.7Nick Mathewson
2016-11-07Merge branch 'maint-0.2.5' into maint-0.2.6Nick Mathewson
2016-11-07Merge branch 'maint-0.2.4' into maint-0.2.5Nick Mathewson