aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMatthias Andree <matthias.andree@gmx.de>2007-01-06 08:45:19 +0000
committerMatthias Andree <matthias.andree@gmx.de>2007-01-06 08:45:19 +0000
commit9537b03945f792454628e3fd2849cd1c761d71b7 (patch)
tree224cbf76a735568e831203b9f99021166b0189ee
parent94c2356830ef291cb88266425637e93ea1d747dc (diff)
downloadfetchmail-9537b03945f792454628e3fd2849cd1c761d71b7.tar.gz
fetchmail-9537b03945f792454628e3fd2849cd1c761d71b7.tar.bz2
fetchmail-9537b03945f792454628e3fd2849cd1c761d71b7.zip
r6396@balu: mandree | 2007-01-06 09:45:01 +0100
Fix typo, only change -> only safe. svn path=/branches/BRANCH_6-3/; revision=5014
-rw-r--r--NEWS2
1 files changed, 1 insertions, 1 deletions
diff --git a/NEWS b/NEWS
index 17ba245a..19e9a584 100644
--- a/NEWS
+++ b/NEWS
@@ -69,7 +69,7 @@ fetchmail 6.3.6 (released 2007-01-04):
Configurations using both ssl and sslcertck however have been semi-safe in
that they would send the password in the clear. The USER/PASS fallback
- problem however applies to these too, so that the password was only change on
+ problem however applies to these too, so that the password was only safe on
trustworthy servers.
* CVE-2006-5974, fetchmail-SA-2006-03.txt: