Make security warnings in the Safe and Opcode modules more direct.

The current "no warranty" text warning against the use of Safe or
Opcode for "security purposes" is somewhat ambiguous. These modules
are not effective sandboxing mechanisms for evaluating untrusted
perl code and should not be used in that manner.

Safe and Opcode are, at best, hardening measures that could be used
in combination with operating system level sandboxing of the perl
interpreter.

Author: lightsey

dist/Safe/Safe.pm

@@ -3,7 +3,7 @@ package Safe;
 use 5.003_11;
 use Scalar::Util qw(reftype refaddr);
 
-$Safe::VERSION = "2.42";
+$Safe::VERSION = "2.43";
 
 # *** Don't declare any lexicals above this point ***
 #
@@ -543,6 +543,13 @@ outside the compartment) placed into the compartment. For example,
 
 =head1 WARNING
 
+The Safe module does not implement an effective sandbox for
+evaluating untrusted code with the perl interpreter.
+
+Bugs in the perl interpreter that could be abused to bypass
+Safe restrictions are not treated as vulnerabilities. See
+L<perlsecpolicy> for additional information.
+
 The authors make B<no warranty>, implied or otherwise, about the
 suitability of this software for safety or security purposes.
 

ext/Opcode/Opcode.pm

@@ -6,7 +6,7 @@ use strict;
 
 our($VERSION, @ISA, @EXPORT_OK);
 
-$VERSION = "1.47";
+$VERSION = "1.48";
 
 use Carp;
 use Exporter ();
@@ -117,6 +117,13 @@ Safe modules for more typical uses.
 
 =head1 WARNING
 
+The Opcode module does not implement an effective sandbox for
+evaluating untrusted code with the perl interpreter.
+
+Bugs in the perl interpreter that could be abused to bypass
+Opcode restrictions are not treated as vulnerabilities. See
+L<perlsecpolicy> for additional information.
+
 The authors make B<no warranty>, implied or otherwise, about the
 suitability of this software for safety or security purposes.