Apply local patches - perl-5.40.1

ok sthen@
sooner rather than later deraadt@

Fix merge issues, remove excess files - match perl-5.40.1 dist

ok sthen@
sooner rather than later deraadt@

Apply local patches - perl-5.38.2

ok gkoehler@
Commit and we'll fix fallout bluhm@
Right away, please deraadt@

Fix merge issues, remove excess files - match perl-5.38.2 dist

ok gkoehler@
Commit and we'll fix fallout bluhm@
Right away, please deraadt@

Apply local patches - perl-5.36.0

OK bluhm@
a good time naddy@

Fix merge issues, remove excess files - match perl-5.36.0 dist

OK bluhm@
a good time naddy@

Apply local patches, remove excess files - perl-5.32.1

OK sthen@

Fix merge issues, remove excess files - match perl-5.32.1 dist

OK sthen@

Apply local patches, remove excess files - perl-5.30.1

Timing is good deraadt@, OK sthen@

Fix merge issues, remove excess files - match perl-5.30.1 dist

Timing is good deraadt@, OK sthen@

Fix Pod::Perldoc::ToMan and use it as the default perldoc formatter

From Andrew Daugherity <andrew.daugherity () gmail ! com>

Corrections to fix and OK millert@, suggestions and OK schwarze@

Fix merge issues, remove excess files - match perl-5.28.1 dist

looking good sthen@, Great! bluhm@

Fix merge issues, remove excess files - match perl-5.24.1 dist

Patch perl CVE-2016-1238

The problem relates to Perl 5 ("perl") loading modules from the
includes directory array ("@INC") in which the last element is the
current directory ("."). That means that,

Patch perl CVE-2016-1238

The problem relates to Perl 5 ("perl") loading modules from the
includes directory array ("@INC") in which the last element is the
current directory ("."). That means that, when "perl" wants to
load a module (during first compilation or during lazy loading of
a module in run-time), perl will look for the module in the current
directory at the end, since '.' is the last include directory in
its array of include directories to seek. The issue is with requiring
libraries that are in "." but are not otherwise installed.

The major problem with this behavior is that it unexpectedly puts
a user at risk whenever they execute any Perl scripts from a directory
that is writable by other accounts on the system. For instance, if
a user is logged in as root and changes directory into /tmp or an
account's home directory, it is possible to now run any shell
commands that are written in C, Python or Ruby without fear.

The same isn't true for any shell commands that are written in Perl,
since a significant proportion of Perl scripts will execute code
in the current working directory whenever they are run. For example,
if a user on a shared system creates the file /tmp/Pod/Perldoc/Toterm.pm,
and then I log in as root, change directory to /tmp, and run "perldoc
perlrun", it will execute the code they have placed in the file.


ok deraadt@

show more ...

Import perl-5.20.1

Import perl-5.18.2

OK espie@ sthen@ deraadt@

import perl 5.16.3 from CPAN - worked on by Andrew Fresh and myself