summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPaul "LeoNerd" Evans <leonerd@leonerd.org.uk>2022-05-19 17:57:04 +0100
committerPaul "LeoNerd" Evans <leonerd@leonerd.org.uk>2022-05-19 22:38:44 +0100
commite8e0a7c59e2615991a7963725a819604a95368b8 (patch)
treefa90ecd7c3f7d3c5fdb4a81e877110ab64202bd8
parent28003a95818e4d096e18c687a8bddd8584656154 (diff)
downloadperl-e8e0a7c59e2615991a7963725a819604a95368b8.tar.gz
Remove documentation references to recent Configure taint changes
-rw-r--r--pod/perlipc.pod6
-rw-r--r--pod/perllocale.pod1
-rw-r--r--pod/perlmodstyle.pod7
-rw-r--r--pod/perlrun.pod7
-rw-r--r--pod/perlsec.pod16
5 files changed, 4 insertions, 33 deletions
diff --git a/pod/perlipc.pod b/pod/perlipc.pod
index 840c2719b0..db1fe3df72 100644
--- a/pod/perlipc.pod
+++ b/pod/perlipc.pod
@@ -1132,9 +1132,9 @@ even if we aren't running setuid or setgid. This is always a good idea
for servers or any program run on behalf of someone else (like CGI
scripts), because it lessens the chances that people from the outside will
be able to compromise your system.
-Note that perl can be built without taint support,
-in which case -T silently does nothing
-(see L<perlsec> for how to check if your perl support taint checking).
+Note that perl can be built without taint support. There are two
+different modes: in one, B<-T> will silently do nothing. In the other
+mode B<-T> results in a fatal error.
Let's look at another TCP client. This one connects to the TCP "time"
service on a number of different machines and shows how far their clocks
diff --git a/pod/perllocale.pod b/pod/perllocale.pod
index 14a5bcb65f..30940a5a1f 100644
--- a/pod/perllocale.pod
+++ b/pod/perllocale.pod
@@ -1162,7 +1162,6 @@ which may be untrustworthy in consequence.
Note that it is possible to compile Perl without taint support,
in which case all taint features silently do nothing.
-See L<perlsec> for how to tell if your perl supports taint checking.
Here is a summary of the tainting behavior of operators and functions
that may be affected by the locale:
diff --git a/pod/perlmodstyle.pod b/pod/perlmodstyle.pod
index 7aa06ef288..c217008250 100644
--- a/pod/perlmodstyle.pod
+++ b/pod/perlmodstyle.pod
@@ -428,13 +428,6 @@ run without generating any warnings. Your module should also handle
taint-checking where appropriate, though this can cause difficulties in
many cases.
-Note though that Perl can be configured to not support taint checking,
-in which case all taint features silently do nothing.
-Your module, and its tests, should support this configuration.
-See L<perlsec> for how to detect whether you're running under
-a perl that doesn't support taint checking.
-
-
=head2 Backwards compatibility
Modules which are "stable" should not break backwards compatibility
diff --git a/pod/perlrun.pod b/pod/perlrun.pod
index 4d60f70063..817e2f2568 100644
--- a/pod/perlrun.pod
+++ b/pod/perlrun.pod
@@ -861,8 +861,7 @@ 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>).
+This has no effect if your perl was built without taint support.
=item B<-T>
X<-T>
@@ -877,10 +876,6 @@ 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>
diff --git a/pod/perlsec.pod b/pod/perlsec.pod
index 5151498d19..8c9f966090 100644
--- a/pod/perlsec.pod
+++ b/pod/perlsec.pod
@@ -60,10 +60,6 @@ Support for taint checks adds an overhead to all Perl programs,
whether or not you're using the taint features.
Perl 5.18 introduced C preprocessor symbols that can
be used to disable the taint features.
-Perl 5.36 introduced added a question for this to Configure,
-to make it easier to build a perl binary without taint support.
-See L</Checking for taint support> below on how to check
-whether your perl supports taint checks.
=over 4
@@ -624,18 +620,6 @@ in mind. It is neither necessary nor sufficient for the same script to
be suitable to run in a traditional set-id arrangement, though many of
the issues overlap.
-=head2 Checking for taint support
-
-To see if your perl has been built with taint support,
-check C<taint_support> in the C<%Config> hash in L<Config>.
-If C<taint_support> doesn't exist in the hash,
-your version of Perl predates this Configure option.
-
- use Config;
- if (!exists($Config{taint_support}) || $Config{taint_support}) {
- print "taint IS supported\n";
- }
-
=head1 SEE ALSO
L<perlrun/ENVIRONMENT> for its description of cleaning up environment