aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--NEWS6
-rw-r--r--fetchmail.man8
2 files changed, 12 insertions, 2 deletions
diff --git a/NEWS b/NEWS
index f6db5654..8f1e410a 100644
--- a/NEWS
+++ b/NEWS
@@ -55,14 +55,16 @@ driver to SMTP. (This requires that we find a POP2 server to test with.)
* Ported to QNX (see the Makefile).
-* Add Michael Scwendt's code for improved sizeticker.
+* Add Michael Schwendt's code for improved sizeticker.
+
+* Improved RFC822 parsing (thanks to Rob Funk).
* Move the per-user lockfile to /tmp so it gets cleared at reboot time.
* Warn users that running concurrent instances of popclient is a bad idea.
* Try USER and HOME to set defaults before going to the password file.
- This should work in Sun NIS environments.
+ This should work better in Sun NIS environments.
3.1:
diff --git a/fetchmail.man b/fetchmail.man
index 1e112838..5e4a610e 100644
--- a/fetchmail.man
+++ b/fetchmail.man
@@ -597,6 +597,14 @@ encouraged people to expose passwords in scripts. Passwords
must now be specified either interactively or in your
.I ~/.poprc
file. The short-form -p option now specifies the protocol to use.
+.PP
+The reason the password isn't stored encrypted is because this doesn't
+actually add protection. Anyone who's acquired permissions to read your
+poprc file will be able to run popclient as you anyway -- and if it's
+your password they're after, they'd be able to use the necessary decoder from
+.I popclient
+itself to get it. All encryption would do in this context is give a
+false sense of security to people who don't think very hard.
.SH SEE ALSO
mail(1), binmail(1), sendmail(8), popd(8),
RFC 937, RFC 1081, RFC 1082, RFC 1225, RFC 1460, RFC 1725.