diff options
| author | Eric S. Raymond <esr@thyrsus.com> | 1996-09-23 05:35:21 +0000 |
|---|---|---|
| committer | Eric S. Raymond <esr@thyrsus.com> | 1996-09-23 05:35:21 +0000 |
| commit | 7776e2819833e302f654f7bfd34ff2c26b63460a (patch) | |
| tree | e52274f3808ccde0a03c8d1fe1cec7123910d60c /fetchmail.man | |
| parent | dd49e2a559ec49086c1061b456c919819fc08f73 (diff) | |
| download | fetchmail-7776e2819833e302f654f7bfd34ff2c26b63460a.tar.gz fetchmail-7776e2819833e302f654f7bfd34ff2c26b63460a.tar.bz2 fetchmail-7776e2819833e302f654f7bfd34ff2c26b63460a.zip | |
Update docs.
svn path=/trunk/; revision=105
Diffstat (limited to 'fetchmail.man')
| -rw-r--r-- | fetchmail.man | 8 |
1 files changed, 8 insertions, 0 deletions
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. |