From 28003a95818e4d096e18c687a8bddd8584656154 Mon Sep 17 00:00:00 2001
From: "Paul \"LeoNerd\" Evans" <leonerd@leonerd.org.uk>
Date: Sun, 1 May 2022 09:54:49 +0100
Subject: Revert "Add Configure question for taint support"

This reverts commit 39f8eb4a21670e6b973dcfc86d0b1339064f5642.

This is because of a variety of issues discussed #19657 and at the PSC
meeting 064 2022-04-22

https://www.nntp.perl.org/group/perl.perl5.porters/2022/04/msg263670.html
---
 Configure | 44 +-------------------------------------------
 1 file changed, 1 insertion(+), 43 deletions(-)

(limited to 'Configure')

diff --git a/Configure b/Configure
index 279844e004..bd96249c07 100755
--- a/Configure
+++ b/Configure
@@ -1333,7 +1333,6 @@ stdchar=''
 d_stdio_stream_array=''
 stdio_stream_array=''
 sysman=''
-taint_support=''
 sGMTIME_max=''
 sGMTIME_min=''
 sLOCALTIME_max=''
@@ -7306,40 +7305,6 @@ esac
 : confusing anyway.
 installstyle=$dflt
 
-: U/perl/taint_support.U - do we want taint support?
-case "$taint_support" in
-    $undef|false|[Nn]*)
-       dflt="n"
-       ;;
-    *)
-       dflt="y"
-       ;;
-esac
-cat >&4 <<EOM
-
-
-Perl can provide a set of special security checks, which are known
-as taint mode.  The most well-known of these is that data derived
-from outside your program should not be trusted ("is tainted")
-until you have checked it.
-
-These days there are many more security considerations, and as a result
-taint mode isn't widely used. But support for it adds a runtime overhead,
-whether or not you use it.  As a result, you can choose to build Perl
-without taint support.
-
-EOM
-rp='Do you want to build Perl with taint support?'
-. ./myread
-case "$ans" in
-$undef|false|n|N)    val="$undef"
-        ccflags="$ccflags -DSILENT_NO_TAINT_SUPPORT"
-        ;;
-*)      val="$define" ;;
-esac
-set taint_support
-eval $setvar
-
 : determine where public executables go
 echo " "
 set dflt bin bin
@@ -7365,13 +7330,7 @@ cat <<EOM
 Would you like to build Perl so that the installation is relocatable, so that
 library paths in @INC are determined relative to the path of the perl binary?
 This is not advised for system Perl installs, or if you need to run setid
-EOM
-if test "X$taint_support" = "X$define"; then
-    echo "scripts or scripts under taint mode." >&4
-else
-    echo "scripts." >&4
-fi
-cat <<EOM
+scripts or scripts under taint mode.
 
 If this doesn't make any sense to you, just accept the default '$dflt'.
 EOM
@@ -25612,7 +25571,6 @@ subversion='$subversion'
 sysman='$sysman'
 sysroot='$sysroot'
 tail='$tail'
-taint_support='$taint_support'
 tar='$tar'
 targetarch='$targetarch'
 targetdir='$targetdir'
-- 
cgit v1.2.1