Initial commit of OpenSPARC T2 design and verification files.

[OpenSPARC-T2-DV] / tools / perl-5.8.0 / man / man1 / perlsec.1

.\" Automatically generated by Pod::Man v1.34, Pod::Parser v1.13
.\"
.\" Standard preamble:
.\" ========================================================================
.de Sh \" Subsection heading
.br
.if t .Sp
.ne 5
.PP
\fB\\$1\fR
.PP
..
.de Sp \" Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
..
.de Vb \" Begin verbatim text
.ft CW
.nf
.ne \\$1
..
.de Ve \" End verbatim text
.ft R
.fi
..
.\" Set up some character translations and predefined strings.  \*(-- will
.\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left
.\" double quote, and \*(R" will give a right double quote.  | will give a
.\" real vertical bar.  \*(C+ will give a nicer C++.  Capital omega is used to
.\" do unbreakable dashes and therefore won't be available.  \*(C` and \*(C'
.\" expand to `' in nroff, nothing in troff, for use with C<>.
.tr \(*W-|\(bv\*(Tr
.ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p'
.ie n \{\
.    ds -- \(*W-
.    ds PI pi
.    if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch
.    if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\"  diablo 12 pitch
.    ds L" ""
.    ds R" ""
.    ds C` ""
.    ds C' ""
'br\}
.el\{\
.    ds -- \|\(em\|
.    ds PI \(*p
.    ds L" ``
.    ds R" ''
'br\}
.\"
.\" If the F register is turned on, we'll generate index entries on stderr for
.\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
.\" entries marked with X<> in POD.  Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
.if \nF \{\
.    de IX
.    tm Index:\\$1\t\\n%\t"\\$2"
..
.    nr % 0
.    rr F
.\}
.\"
.\" For nroff, turn off justification.  Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.hy 0
.if n .na
.\"
.\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
.\" Fear.  Run.  Save yourself.  No user-serviceable parts.
.    \" fudge factors for nroff and troff
.if n \{\
.    ds #H 0
.    ds #V .8m
.    ds #F .3m
.    ds #[ \f1
.    ds #] \fP
.\}
.if t \{\
.    ds #H ((1u-(\\\\n(.fu%2u))*.13m)
.    ds #V .6m
.    ds #F 0
.    ds #[ \&
.    ds #] \&
.\}
.    \" simple accents for nroff and troff
.if n \{\
.    ds ' \&
.    ds ` \&
.    ds ^ \&
.    ds , \&
.    ds ~ ~
.    ds /
.\}
.if t \{\
.    ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u"
.    ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u'
.    ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u'
.    ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u'
.    ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u'
.    ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u'
.\}
.    \" troff and (daisy-wheel) nroff accents
.ds : \\k:\h'-(\\n(.wu*8/10-\*(#H+.1m+\*(#F)'\v'-\*(#V'\z.\h'.2m+\*(#F'.\h'|\\n:u'\v'\*(#V'
.ds 8 \h'\*(#H'\(*b\h'-\*(#H'
.ds o \\k:\h'-(\\n(.wu+\w'\(de'u-\*(#H)/2u'\v'-.3n'\*(#[\z\(de\v'.3n'\h'|\\n:u'\*(#]
.ds d- \h'\*(#H'\(pd\h'-\w'~'u'\v'-.25m'\f2\(hy\fP\v'.25m'\h'-\*(#H'
.ds D- D\\k:\h'-\w'D'u'\v'-.11m'\z\(hy\v'.11m'\h'|\\n:u'
.ds th \*(#[\v'.3m'\s+1I\s-1\v'-.3m'\h'-(\w'I'u*2/3)'\s-1o\s+1\*(#]
.ds Th \*(#[\s+2I\s-2\h'-\w'I'u*3/5'\v'-.3m'o\v'.3m'\*(#]
.ds ae a\h'-(\w'a'u*4/10)'e
.ds Ae A\h'-(\w'A'u*4/10)'E
.    \" corrections for vroff
.if v .ds ~ \\k:\h'-(\\n(.wu*9/10-\*(#H)'\s-2\u~\d\s+2\h'|\\n:u'
.if v .ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'\v'-.4m'^\v'.4m'\h'|\\n:u'
.    \" for low resolution devices (crt and lpr)
.if \n(.H>23 .if \n(.V>19 \
\{\
.    ds : e
.    ds 8 ss
.    ds o a
.    ds d- d\h'-1'\(ga
.    ds D- D\h'-1'\(hy
.    ds th \o'bp'
.    ds Th \o'LP'
.    ds ae ae
.    ds Ae AE
.\}
.rm #[ #] #H #V #F C
.\" ========================================================================
.\"
.IX Title "PERLSEC 1"
.TH PERLSEC 1 "2002-06-08" "perl v5.8.0" "Perl Programmers Reference Guide"
.SH "NAME"
perlsec \- Perl security
.SH "DESCRIPTION"
.IX Header "DESCRIPTION"
Perl is designed to make it easy to program securely even when running
with extra privileges, like setuid or setgid programs.  Unlike most
command line shells, which are based on multiple substitution passes on
each line of the script, Perl uses a more conventional evaluation scheme
with fewer hidden snags.  Additionally, because the language has more
builtin functionality, it can rely less upon external (and possibly
untrustworthy) programs to accomplish its purposes.
.PP
Perl automatically enables a set of special security checks, called \fItaint
mode\fR, when it detects its program running with differing real and effective
user or group IDs.  The setuid bit in Unix permissions is mode 04000, the
setgid bit mode 02000; either or both may be set.  You can also enable taint
mode explicitly by using the \fB\-T\fR command line flag. This flag is
\&\fIstrongly\fR suggested for server programs and any program run on behalf of
someone else, such as a \s-1CGI\s0 script. Once taint mode is on, it's on for
the remainder of your script.
.PP
While in this mode, Perl takes special precautions called \fItaint
checks\fR to prevent both obvious and subtle traps.  Some of these checks
are reasonably simple, such as verifying that path directories aren't
writable by others; careful programmers have always used checks like
these.  Other checks, however, are best supported by the language itself,
and it is these checks especially that contribute to making a set-id Perl
program more secure than the corresponding C program.
.PP
You may not use data derived from outside your program to affect
something else outside your program\*(--at least, not by accident.  All
command line arguments, environment variables, locale information (see
perllocale), results of certain system calls (\fIreaddir()\fR,
\&\fIreadlink()\fR, the variable of \fIshmread()\fR, the messages returned by
\&\fImsgrcv()\fR, the password, gcos and shell fields returned by the
\&\fIgetpwxxx()\fR calls), and all file input are marked as \*(L"tainted\*(R".
Tainted data may not be used directly or indirectly in any command
that invokes a sub\-shell, nor in any command that modifies files,
directories, or processes, \fBwith the following exceptions\fR:
.IP "\(bu" 4
If you pass more than one argument to either \f(CW\*(C`system\*(C'\fR or \f(CW\*(C`exec\*(C'\fR,
the arguments are checked for taintedness \fBbut\fR the operation will still
be attempted, emitting an optional warning.  This will be fatal in a 
future version of perl so do not rely on it to bypass the tainting 
mechanism.
.IP "\(bu" 4
Arguments to \f(CW\*(C`print\*(C'\fR and \f(CW\*(C`syswrite\*(C'\fR are \fBnot\fR checked for taintedness.
.IP "\(bu" 4
Symbolic methods
.Sp
.Vb 1
\&    $obj->$method(@args);
.Ve
.Sp
and symbolic sub references
.Sp
.Vb 2
\&    &{$foo}(@args);
\&    $foo->(@args);
.Ve
.Sp
are not checked for taintedness.  This requires extra carefulness
unless you want external data to affect your control flow.  Unless
you carefully limit what these symbolic values are, people are able
to call functions \fBoutside\fR your Perl code, such as POSIX::system,
in which case they are able to run arbitrary external code.
.PP
The value of an expression containing tainted data will itself be
tainted, even if it is logically impossible for the tainted data to
affect the value.
.PP
Because taintedness is associated with each scalar value, some
elements of an array can be tainted and others not.
.PP
For example:
.PP
.Vb 8
\&    $arg = shift;               # $arg is tainted
\&    $hid = $arg, 'bar';         # $hid is also tainted
\&    $line = <>;                 # Tainted
\&    $line = <STDIN>;            # Also tainted
\&    open FOO, "/home/me/bar" or die $!;
\&    $line = <FOO>;              # Still tainted
\&    $path = $ENV{'PATH'};       # Tainted, but see below
\&    $data = 'abc';              # Not tainted
.Ve
.PP
.Vb 5
\&    system "echo $arg";         # Insecure
\&    system "/bin/echo", $arg;   # Allowed but considered insecure
\&                                # (Perl doesn't know about /bin/echo)
\&    system "echo $hid";         # Insecure
\&    system "echo $data";        # Insecure until PATH set
.Ve
.PP
.Vb 1
\&    $path = $ENV{'PATH'};       # $path now tainted
.Ve
.PP
.Vb 2
\&    $ENV{'PATH'} = '/bin:/usr/bin';
\&    delete @ENV{'IFS', 'CDPATH', 'ENV', 'BASH_ENV'};
.Ve
.PP
.Vb 2
\&    $path = $ENV{'PATH'};       # $path now NOT tainted
\&    system "echo $data";        # Is secure now!
.Ve
.PP
.Vb 2
\&    open(FOO, "< $arg");        # OK - read-only file
\&    open(FOO, "> $arg");        # Not OK - trying to write
.Ve
.PP
.Vb 3
\&    open(FOO,"echo $arg|");     # Not OK
\&    open(FOO,"-|")
\&        or exec 'echo', $arg;   # Allowed but not really OK
.Ve
.PP
.Vb 1
\&    $shout = `echo $arg`;       # Insecure, $shout now tainted
.Ve
.PP
.Vb 2
\&    unlink $data, $arg;         # Insecure
\&    umask $arg;                 # Insecure
.Ve
.PP
.Vb 3
\&    exec "echo $arg";           # Insecure
\&    exec "echo", $arg;          # Allowed but considered insecure
\&    exec "sh", '-c', $arg;      # Considered secure, alas!
.Ve
.PP
.Vb 2
\&    @files = <*.c>;             # insecure (uses readdir() or similar)
\&    @files = glob('*.c');       # insecure (uses readdir() or similar)
.Ve
.PP
.Vb 4
\&    # In Perl releases older than 5.6.0 the <*.c> and glob('*.c') would
\&    # have used an external program to do the filename expansion; but in
\&    # either case the result is tainted since the list of filenames comes
\&    # from outside of the program.
.Ve
.PP
.Vb 2
\&    $bad = ($arg, 23);          # $bad will be tainted
\&    $arg, `true`;               # Insecure (although it isn't really)
.Ve
.PP
If you try to do something insecure, you will get a fatal error saying
something like \*(L"Insecure dependency\*(R" or \*(L"Insecure \f(CW$ENV\fR{\s-1PATH\s0}\*(R".  Note that you
can still write an insecure \fBsystem\fR or \fBexec\fR, but only by explicitly
doing something like the \*(L"considered secure\*(R" example above.  This will not
be possible in a future version of Perl.
.Sh "Laundering and Detecting Tainted Data"
.IX Subsection "Laundering and Detecting Tainted Data"
To test whether a variable contains tainted data, and whose use would
thus trigger an \*(L"Insecure dependency\*(R" message, you can use the
\&\fItainted()\fR function of the Scalar::Util module, available in your
nearby \s-1CPAN\s0 mirror, and included in Perl starting from the release 5.8.0.
Or you may be able to use the following \fI\fIis_tainted()\fI\fR function.
.PP
.Vb 3
\&    sub is_tainted {
\&        return ! eval { eval("#" . substr(join("", @_), 0, 0)); 1 };
\&    }
.Ve
.PP
This function makes use of the fact that the presence of tainted data
anywhere within an expression renders the entire expression tainted.  It
would be inefficient for every operator to test every argument for
taintedness.  Instead, the slightly more efficient and conservative
approach is used that if any tainted value has been accessed within the
same expression, the whole expression is considered tainted.
.PP
But testing for taintedness gets you only so far.  Sometimes you have just
to clear your data's taintedness.  The only way to bypass the tainting
mechanism is by referencing subpatterns from a regular expression match.
Perl presumes that if you reference a substring using \f(CW$1\fR, \f(CW$2\fR, etc., that
you knew what you were doing when you wrote the pattern.  That means using
a bit of thought\*(--don't just blindly untaint anything, or you defeat the
entire mechanism.  It's better to verify that the variable has only good
characters (for certain values of \*(L"good\*(R") rather than checking whether it
has any bad characters.  That's because it's far too easy to miss bad
characters that you never thought of.
.PP
Here's a test to make sure that the data contains nothing but \*(L"word\*(R"
characters (alphabetics, numerics, and underscores), a hyphen, an at sign,
or a dot.
.PP
.Vb 5
\&    if ($data =~ /^([-\e@\ew.]+)$/) {
\&        $data = $1;                     # $data now untainted
\&    } else {
\&        die "Bad data in $data";        # log this somewhere
\&    }
.Ve
.PP
This is fairly secure because \f(CW\*(C`/\ew+/\*(C'\fR doesn't normally match shell
metacharacters, nor are dot, dash, or at going to mean something special
to the shell.  Use of \f(CW\*(C`/.+/\*(C'\fR 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 \fIonly\fR mechanism for
untainting dirty data, unless you use the strategy detailed below to fork
a child of lesser privilege.
.PP
The example does not untaint \f(CW$data\fR if \f(CW\*(C`use locale\*(C'\fR is in effect,
because the characters matched by \f(CW\*(C`\ew\*(C'\fR are determined by the locale.
Perl considers that locale definitions are untrustworthy because they
contain data from outside the program.  If you are writing a
locale-aware program, and want to launder data with a regular expression
containing \f(CW\*(C`\ew\*(C'\fR, put \f(CW\*(C`no locale\*(C'\fR ahead of the expression in the same
block.  See \*(L"\s-1SECURITY\s0\*(R" in perllocale for further discussion and examples.
.ie n .Sh "Switches On the ""#!"" Line"
.el .Sh "Switches On the ``#!'' Line"
.IX Subsection "Switches On the #! Line"
When you make a script executable, in order to make it usable as a
command, the system will pass switches to perl from the script's #!
line.  Perl checks that any command line switches given to a setuid
(or setgid) script actually match the ones set on the #! line.  Some
Unix and Unix-like environments impose a one-switch limit on the #!
line, so you may need to use something like \f(CW\*(C`\-wU\*(C'\fR instead of \f(CW\*(C`\-w \-U\*(C'\fR
under such systems.  (This issue should arise only in Unix or
Unix-like environments that support #! and setuid or setgid scripts.)
.Sh "Cleaning Up Your Path"
.IX Subsection "Cleaning Up Your Path"
For "Insecure \f(CW$ENV{PATH}\fR" messages, you need to set \f(CW$ENV{'PATH'}\fR to a
known value, and each directory in the path must be non-writable by others
than its owner and group.  You may be surprised to get this message even
if the pathname to your executable is fully qualified.  This is \fInot\fR
generated because you didn't supply a full path to the program; instead,
it's generated because you never set your \s-1PATH\s0 environment variable, or
you didn't set it to something that was safe.  Because Perl can't
guarantee that the executable in question isn't itself going to turn
around and execute some other program that is dependent on your \s-1PATH\s0, it
makes sure you set the \s-1PATH\s0.
.PP
The \s-1PATH\s0 isn't the only environment variable which can cause problems.
Because some shells may use the variables \s-1IFS\s0, \s-1CDPATH\s0, \s-1ENV\s0, and
\&\s-1BASH_ENV\s0, Perl checks that those are either empty or untainted when
starting subprocesses. You may wish to add something like this to your
setid and taint-checking scripts.
.PP
.Vb 1
\&    delete @ENV{qw(IFS CDPATH ENV BASH_ENV)};   # Make %ENV safer
.Ve
.PP
It's also possible to get into trouble with other operations that don't
care whether they use tainted values.  Make judicious use of the file
tests in dealing with any user-supplied filenames.  When possible, do
opens and such \fBafter\fR properly dropping any special user (or group!)
privileges. Perl doesn't prevent you from opening tainted filenames for reading,
so be careful what you print out.  The tainting mechanism is intended to
prevent stupid mistakes, not to remove the need for thought.
.PP
Perl does not call the shell to expand wild cards when you pass \fBsystem\fR
and \fBexec\fR explicit parameter lists instead of strings with possible shell
wildcards in them.  Unfortunately, the \fBopen\fR, \fBglob\fR, and
backtick functions provide no such alternate calling convention, so more
subterfuge will be required.
.PP
Perl provides a reasonably safe way to open a file or pipe from a setuid
or setgid program: just create a child process with reduced privilege who
does the dirty work for you.  First, fork a child using the special
\&\fBopen\fR syntax that connects the parent and child by a pipe.  Now the
child resets its \s-1ID\s0 set and any other per-process attributes, like
environment variables, umasks, current working directories, back to the
originals or known safe values.  Then the child process, which no longer
has any special permissions, does the \fBopen\fR or other system call.
Finally, the child passes the data it managed to access back to the
parent.  Because the file or pipe was opened in the child while running
under less privilege than the parent, it's not apt to be tricked into
doing something it shouldn't.
.PP
Here's a way to do backticks reasonably safely.  Notice how the \fBexec\fR is
not called with a string that the shell could expand.  This is by far the
best way to call something that might be subjected to shell escapes: just
never call the shell at all.  
.PP
.Vb 25
\&        use English '-no_match_vars';
\&        die "Can't fork: $!" unless defined($pid = open(KID, "-|"));
\&        if ($pid) {           # parent
\&            while (<KID>) {
\&                # do something
\&            }
\&            close KID;
\&        } else {
\&            my @temp     = ($EUID, $EGID);
\&            my $orig_uid = $UID;
\&            my $orig_gid = $GID;
\&            $EUID = $UID;
\&            $EGID = $GID;
\&            # Drop privileges
\&            $UID  = $orig_uid;
\&            $GID  = $orig_gid;
\&            # Make sure privs are really gone
\&            ($EUID, $EGID) = @temp;
\&            die "Can't drop privileges"
\&                unless $UID == $EUID  && $GID eq $EGID;
\&            $ENV{PATH} = "/bin:/usr/bin"; # Minimal PATH.
\&            # Consider sanitizing the environment even more.
\&            exec 'myprog', 'arg1', 'arg2'
\&                or die "can't exec myprog: $!";
\&        }
.Ve
.PP
A similar strategy would work for wildcard expansion via \f(CW\*(C`glob\*(C'\fR, although
you can use \f(CW\*(C`readdir\*(C'\fR instead.
.PP
Taint checking is most useful when although you trust yourself not to have
written a program to give away the farm, you don't necessarily trust those
who end up using it not to try to trick it into doing something bad.  This
is the kind of security checking that's useful for set-id programs and
programs launched on someone else's behalf, like \s-1CGI\s0 programs.
.PP
This is quite different, however, from not even trusting the writer of the
code not to try to do something evil.  That's the kind of trust needed
when someone hands you a program you've never seen before and says, \*(L"Here,
run this.\*(R"  For that kind of safety, check out the Safe module,
included standard in the Perl distribution.  This module allows the
programmer to set up special compartments in which all system operations
are trapped and namespace access is carefully controlled.
.Sh "Security Bugs"
.IX Subsection "Security Bugs"
Beyond the obvious problems that stem from giving special privileges to
systems as flexible as scripts, on many versions of Unix, set-id scripts
are inherently insecure right from the start.  The problem is a race
condition in the kernel.  Between the time the kernel opens the file to
see which interpreter to run and when the (now\-set\-id) interpreter turns
around and reopens the file to interpret it, the file in question may have
changed, especially if you have symbolic links on your system.
.PP
Fortunately, sometimes this kernel \*(L"feature\*(R" can be disabled.
Unfortunately, there are two ways to disable it.  The system can simply
outlaw scripts with any set-id bit set, which doesn't help much.
Alternately, it can simply ignore the set-id bits on scripts.  If the
latter is true, Perl can emulate the setuid and setgid mechanism when it
notices the otherwise useless setuid/gid bits on Perl scripts.  It does
this via a special executable called \fBsuidperl\fR that is automatically
invoked for you if it's needed.
.PP
However, if the kernel set-id script feature isn't disabled, Perl will
complain loudly that your set-id script is insecure.  You'll need to
either disable the kernel set-id script feature, or put a C wrapper around
the script.  A C wrapper is just a compiled program that does nothing
except call your Perl program.   Compiled programs are not subject to the
kernel bug that plagues set-id scripts.  Here's a simple wrapper, written
in C:
.PP
.Vb 6
\&    #define REAL_PATH "/path/to/script"
\&    main(ac, av)
\&        char **av;
\&    {
\&        execv(REAL_PATH, av);
\&    }
.Ve
.PP
Compile this wrapper into a binary executable and then make \fIit\fR rather
than your script setuid or setgid.
.PP
In recent years, vendors have begun to supply systems free of this
inherent security bug.  On such systems, when the kernel passes the name
of the set-id script to open to the interpreter, rather than using a
pathname subject to meddling, it instead passes \fI/dev/fd/3\fR.  This is a
special file already opened on the script, so that there can be no race
condition for evil scripts to exploit.  On these systems, Perl should be
compiled with \f(CW\*(C`\-DSETUID_SCRIPTS_ARE_SECURE_NOW\*(C'\fR.  The \fBConfigure\fR
program that builds Perl tries to figure this out for itself, so you
should never have to specify this yourself.  Most modern releases of
SysVr4 and \s-1BSD\s0 4.4 use this approach to avoid the kernel race condition.
.PP
Prior to release 5.6.1 of Perl, bugs in the code of \fBsuidperl\fR could
introduce a security hole.
.Sh "Protecting Your Programs"
.IX Subsection "Protecting Your Programs"
There are a number of ways to hide the source to your Perl programs,
with varying levels of \*(L"security\*(R".
.PP
First of all, however, you \fIcan't\fR take away read permission, because
the source code has to be readable in order to be compiled and
interpreted.  (That doesn't mean that a \s-1CGI\s0 script's source is
readable by people on the web, though.)  So you have to leave the
permissions at the socially friendly 0755 level.  This lets 
people on your local system only see your source.
.PP
Some people mistakenly regard this as a security problem.  If your program does
insecure things, and relies on people not knowing how to exploit those
insecurities, it is not secure.  It is often possible for someone to
determine the insecure things and exploit them without viewing the
source.  Security through obscurity, the name for hiding your bugs
instead of fixing them, is little security indeed.
.PP
You can try using encryption via source filters (Filter::* from \s-1CPAN\s0,
or Filter::Util::Call and Filter::Simple since Perl 5.8).
But crackers might be able to decrypt it.  You can try using the byte
code compiler and interpreter described below, but crackers might be
able to de-compile it.  You can try using the native-code compiler
described below, but crackers might be able to disassemble it.  These
pose varying degrees of difficulty to people wanting to get at your
code, but none can definitively conceal it (this is true of every
language, not just Perl).
.PP
If you're concerned about people profiting from your code, then the
bottom line is that nothing but a restrictive licence will give you
legal security.  License your software and pepper it with threatening
statements like \*(L"This is unpublished proprietary software of \s-1XYZ\s0 Corp.
Your access to it does not give you permission to use it blah blah
blah.\*(R"  You should see a lawyer to be sure your licence's wording will
stand up in court.
.Sh "Unicode"
.IX Subsection "Unicode"
Unicode is a new and complex technology and one may easily overlook
certain security pitfalls.  See perluniintro for an overview and
perlunicode for details, and \*(L"Security Implications of Unicode\*(R" in perlunicode for security implications in particular.
.SH "SEE ALSO"
.IX Header "SEE ALSO"
perlrun for its description of cleaning up environment variables.