From: Andrew Pimlott <pimlott@idiomtech.com>
Date: Thu, 5 Oct 2000 13:20:58 +0000 (-0400)
Subject: [ID 20001005.004] doc bug: perlsec misleading re file output
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=b7ee89cee3c5aae4c446f4045b031f8bf83c927e;p=p5sagit%2Fp5-mst-13.2.git

[ID 20001005.004] doc bug: perlsec misleading re file output
Message-Id: <m13hEhW-000SEmC@nolfolan.idiomtech.com>

p4raw-id: //depot/perl@7515
---

diff --git a/pod/perlsec.pod b/pod/perlsec.pod
index 6b50b92..16b439c 100644
--- a/pod/perlsec.pod
+++ b/pod/perlsec.pod
@@ -38,9 +38,22 @@ msgrcv(), the password, gcos and shell fields returned by the
 getpwxxx() calls), and all file input are marked as "tainted".
 Tainted data may not be used directly or indirectly in any command
 that invokes a sub-shell, nor in any command that modifies files,
-directories, or processes. (B<Important exception>: If you pass a list
-of arguments to either C<system> or C<exec>, the elements of that list
-are B<NOT> checked for taintedness.) Any variable set to a value
+directories, or processes, B<with the following exceptions>:
+
+=over 4
+
+=item *
+
+If you pass a list of arguments to either C<system> or C<exec>,
+the elements of that list are B<not> checked for taintedness.
+
+=item *
+
+Arguments to C<print> and C<syswrite> are B<not> checked for taintedness.
+
+=back
+
+Any variable set to a value
 derived from tainted data will itself be tainted, even if it is
 logically impossible for the tainted data to alter the variable.
 Because taintedness is associated with each scalar value, some