aboutsummaryrefslogtreecommitdiff
path: root/changes/bug20384
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2017-02-23 11:16:31 -0500
committerNick Mathewson <nickm@torproject.org>2017-02-23 11:16:31 -0500
commita84f923e899853dedf3ac05ac3820aad1910ae48 (patch)
treef78520ded94943e9e7d530dfdc4fb4596cc14b8a /changes/bug20384
parent2e03c02b74d41266972660de76a3f30739df45e4 (diff)
downloadtor-a84f923e899853dedf3ac05ac3820aad1910ae48.tar.gz
tor-a84f923e899853dedf3ac05ac3820aad1910ae48.zip
Begin an 0.2.4.28 changelog.
To build this changelog, I've gone through the entries in release-0.2.4's changes subdirectory, and looked up the ChangeLog entry for each. I have not sorted them yet.
Diffstat (limited to 'changes/bug20384')
-rw-r--r--changes/bug2038410
1 files changed, 0 insertions, 10 deletions
diff --git a/changes/bug20384 b/changes/bug20384
deleted file mode 100644
index 591015ad94..0000000000
--- a/changes/bug20384
+++ /dev/null
@@ -1,10 +0,0 @@
- o Major features (security fixes):
- - Prevent a class of security bugs caused by treating the contents
- of a buffer chunk as if they were a NUL-terminated string. At
- least one such bug seems to be present in all currently used
- versions of Tor, and would allow an attacker to remotely crash
- most Tor instances, especially those compiled with extra compiler
- hardening. With this defense in place, such bugs can't crash Tor,
- though we should still fix them as they occur. Closes ticket
- 20384 (TROVE-2016-10-001).
-