summaryrefslogtreecommitdiff
path: root/pod/perlrun.pod
diff options
context:
space:
mode:
authorNeil Bowers <neilb@neilb.org>2022-03-16 23:50:01 +0000
committerPaul Evans <leonerd@leonerd.org.uk>2022-04-20 11:38:21 +0100
commit7c90a9467d090b303d2a2b8745b0fad04426d07b (patch)
tree3299ce72fe77548e70918d473feddc58dfc5803c /pod/perlrun.pod
parent774c7748146e99348eefc95bc735a36a2626d090 (diff)
downloadperl-7c90a9467d090b303d2a2b8745b0fad04426d07b.tar.gz
Doc changes to reflect that perl might not support taint
The central doc change is in perlsec.pod. This not only explains that you can build a perl that doesn't support taint, but shows how you can check whether your perl supports taint or not. The other doc changes are mainly to note that taint might not be supported, and to refer the reader to perlsec for more details.
Diffstat (limited to 'pod/perlrun.pod')
-rw-r--r--pod/perlrun.pod7
1 files changed, 7 insertions, 0 deletions
diff --git a/pod/perlrun.pod b/pod/perlrun.pod
index 3202e13c94..3dd7293b66 100644
--- a/pod/perlrun.pod
+++ b/pod/perlrun.pod
@@ -861,6 +861,9 @@ used I<only> as a temporary development aid while securing legacy code:
for real production code and for new secure code written from scratch,
always use the real L</-T>.
+This has no effect if your perl was built without taint support
+(see L<perlsec>).
+
=item B<-T>
X<-T>
@@ -874,6 +877,10 @@ seen by Perl quite early; usually this means it must appear early
on the command line or in the C<#!> line for systems which support
that construct.
+If your perl has been built without taint support, then this option
+has no effect. See L<perlsec> for how to check whether your perl
+supports taint checking.
+
=item B<-u>
X<-u>