From a4b95084e82c29e57b09a9ae4687aa4867a72e98 Mon Sep 17 00:00:00 2001 From: hniksic Date: Sun, 8 Feb 2004 02:50:13 -0800 Subject: [PATCH] [svn] Put @item contents on a separate line. --- doc/ChangeLog | 6 ++++++ doc/wget.texi | 12 ++++++------ 2 files changed, 12 insertions(+), 6 deletions(-) diff --git a/doc/ChangeLog b/doc/ChangeLog index 28525b1e..fc40b9af 100644 --- a/doc/ChangeLog +++ b/doc/ChangeLog @@ -1,3 +1,9 @@ +2004-02-08 Hrvoje Niksic + + * wget.texi (Security Considerations): Put @item contents on a + separate line. + Reported by Ted Rodriguez-Bell. + 2004-02-06 Hrvoje Niksic * wget.texi (Wgetrc Commands): Document --no-http-keep-alive and diff --git a/doc/wget.texi b/doc/wget.texi index 3c14d1ca..543cd628 100644 --- a/doc/wget.texi +++ b/doc/wget.texi @@ -3085,12 +3085,12 @@ through the network, which may present a security problem. Here are the main issues, and some solutions. @enumerate -@item The passwords on the command line are visible using @code{ps}. -The best way around it is to use @code{wget -i -} and feed the @sc{url}s -to Wget's standard input, each on a separate line, terminated by -@kbd{C-d}. Another workaround is to use @file{.netrc} to store -passwords; however, storing unencrypted passwords is also considered a -security risk. +@item +The passwords on the command line are visible using @code{ps}. The best +way around it is to use @code{wget -i -} and feed the @sc{url}s to +Wget's standard input, each on a separate line, terminated by @kbd{C-d}. +Another workaround is to use @file{.netrc} to store passwords; however, +storing unencrypted passwords is also considered a security risk. @item Using the insecure @dfn{basic} authentication scheme, unencrypted -- 2.39.2