aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMatthias Andree <matthias.andree@gmx.de>2012-08-13 22:05:52 +0200
committerMatthias Andree <matthias.andree@gmx.de>2012-08-13 22:05:52 +0200
commit3325c5bf0c6e638fe98557c4d08c48ac9343e7d4 (patch)
tree4e9a6fb3dc80c7fa5bc0131cc4d692d29b006811
parentadd2f3c414fba8308552cd565cd4fcdb2865e032 (diff)
downloadfetchmail-3325c5bf0c6e638fe98557c4d08c48ac9343e7d4.tar.gz
fetchmail-3325c5bf0c6e638fe98557c4d08c48ac9343e7d4.tar.bz2
fetchmail-3325c5bf0c6e638fe98557c4d08c48ac9343e7d4.zip
reword
-rw-r--r--fetchmail-SA-2012-02.txt5
1 files changed, 3 insertions, 2 deletions
diff --git a/fetchmail-SA-2012-02.txt b/fetchmail-SA-2012-02.txt
index 18adfdb9..c6dad70f 100644
--- a/fetchmail-SA-2012-02.txt
+++ b/fetchmail-SA-2012-02.txt
@@ -51,8 +51,9 @@ Fetchmail version 5.0.8 added NTLM support. This code sent the NTLM
authentication request, but never checked if the received response was
NTLM protocol exchange, or a server-side error message. Instead,
fetchmail tried to decode the error message as though it were
-base64-encoded protocol exchange, and could then segfault depending of
-buffer contents, while reading data from bad memory locations.
+base64-encoded protocol exchange, and could then segfault, subject to
+verbosity and other circumstances, while reading data from bad memory
+locations.
3. Solution