diff options
| author | Gurusamy Sarathy <gsar@cpan.org> | 1999-05-24 07:24:11 +0000 |
|---|---|---|
| committer | Gurusamy Sarathy <gsar@cpan.org> | 1999-05-24 07:24:11 +0000 |
| commit | 19799a22062ef658e4ac543ea06fa9193323512a (patch) | |
| tree | ae9ae04d1351eb1dbbc2ea3cfe207cf056e56371 /pod/perlsec.pod | |
| parent | d92eb7b0e84a41728b3fbb642691f159dbe28882 (diff) | |
| download | perl-19799a22062ef658e4ac543ea06fa9193323512a.tar.gz | |
major pod update from Tom Christiansen
p4raw-id: //depot/perl@3460
Diffstat (limited to 'pod/perlsec.pod')
| -rw-r--r-- | pod/perlsec.pod | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/pod/perlsec.pod b/pod/perlsec.pod index 0b22acd9cd..212879af93 100644 --- a/pod/perlsec.pod +++ b/pod/perlsec.pod @@ -139,7 +139,7 @@ metacharacters, nor are dot, dash, or at going to mean something special to the shell. Use of C</.+/> would have been insecure in theory because it lets everything through, but Perl doesn't check for that. The lesson is that when untainting, you must be exceedingly careful with your patterns. -Laundering data using regular expression is the I<ONLY> mechanism for +Laundering data using regular expression is the I<only> mechanism for untainting dirty data, unless you use the strategy detailed below to fork a child of lesser privilege. |