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@

help the debugger look in ports for external parts like PadWalker
and Readline.

feedback and okay afresh1@

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

OK sthen@

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

Timing is good deraadt@, OK sthen@

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, 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@

Update to perl 5.20.3

OK bluhm@

branches: 1.18.4; 1.18.6;
Fix merge conflicts, remove extra files, match upstream perl-5.20.1

ok deraadt@ sthen@ espie@ miod@

Merge perl-5.18.2 plus local patches, remove old files

OK espie@ sthen@ deraadt@

merge/resolve conflicts
(some more to do after this one)

merge in perl 5.12.2 plus local changes

Merge in some local changes that got lost.

Merge in perl 5.10.1

fix conflicts and merge in local changes to perl 5.10.0

merge in perl 5.8.8

sync in-tree perl with 5.8.6

merge 5.8.5 into HEAD
remove now-unused files
crank libperl shared library major number
update Makefile.bsd-wrapper
tweak openbsd hints file for arm and m68k

merge local changes into perl-5.8.3

Resolve conflicts for perl 5.8.2, remove old files, and add OpenBSD-specific scaffolding

Resolve conflicts, remove old files, merge local changes

merge in perl 5.6.1 with our local changes

perl-5.6.0 + local changes

perl5.005_03 (stock)

perl 5.004_04

branches: 1.1.1;
Initial revision

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@

help the debugger look in ports for external parts like PadWalker
and Readline.

feedback and okay afresh1@

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

OK sthen@

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

Timing is good deraadt@, OK sthen@

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, 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@

Update to perl 5.20.3

OK bluhm@

branches: 1.18.4; 1.18.6;
Fix merge conflicts, remove extra files, match upstream perl-5.20.1

ok deraadt@ sthen@ espie@ miod@

Merge perl-5.18.2 plus local patches, remove old files

OK espie@ sthen@ deraadt@

merge/resolve conflicts
(some more to do after this one)

merge in perl 5.12.2 plus local changes

Merge in some local changes that got lost.

Merge in perl 5.10.1

fix conflicts and merge in local changes to perl 5.10.0

merge in perl 5.8.8

sync in-tree perl with 5.8.6

merge 5.8.5 into HEAD
remove now-unused files
crank libperl shared library major number
update Makefile.bsd-wrapper
tweak openbsd hints file for arm and m68k

merge local changes into perl-5.8.3

Resolve conflicts for perl 5.8.2, remove old files, and add OpenBSD-specific scaffolding

Resolve conflicts, remove old files, merge local changes

merge in perl 5.6.1 with our local changes

perl-5.6.0 + local changes

perl5.005_03 (stock)

perl 5.004_04

branches: 1.1.1;
Initial revision

help the debugger look in ports for external parts like PadWalker
and Readline.

feedback and okay afresh1@

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

OK sthen@

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

Timing is good deraadt@, OK sthen@

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, 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@

Update to perl 5.20.3

OK bluhm@

branches: 1.18.4; 1.18.6;
Fix merge conflicts, remove extra files, match upstream perl-5.20.1

ok deraadt@ sthen@ espie@ miod@

Merge perl-5.18.2 plus local patches, remove old files

OK espie@ sthen@ deraadt@

merge/resolve conflicts
(some more to do after this one)

merge in perl 5.12.2 plus local changes

Merge in some local changes that got lost.

Merge in perl 5.10.1

fix conflicts and merge in local changes to perl 5.10.0

merge in perl 5.8.8

sync in-tree perl with 5.8.6

merge 5.8.5 into HEAD
remove now-unused files
crank libperl shared library major number
update Makefile.bsd-wrapper
tweak openbsd hints file for arm and m68k

merge local changes into perl-5.8.3

Resolve conflicts for perl 5.8.2, remove old files, and add OpenBSD-specific scaffolding

Resolve conflicts, remove old files, merge local changes

merge in perl 5.6.1 with our local changes

perl-5.6.0 + local changes

perl5.005_03 (stock)

perl 5.004_04

branches: 1.1.1;
Initial revision

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

OK sthen@

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

Timing is good deraadt@, OK sthen@

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, 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@

Update to perl 5.20.3

OK bluhm@

branches: 1.18.4; 1.18.6;
Fix merge conflicts, remove extra files, match upstream perl-5.20.1

ok deraadt@ sthen@ espie@ miod@

Merge perl-5.18.2 plus local patches, remove old files

OK espie@ sthen@ deraadt@

merge/resolve conflicts
(some more to do after this one)

merge in perl 5.12.2 plus local changes

Merge in some local changes that got lost.

Merge in perl 5.10.1

fix conflicts and merge in local changes to perl 5.10.0

merge in perl 5.8.8

sync in-tree perl with 5.8.6

merge 5.8.5 into HEAD
remove now-unused files
crank libperl shared library major number
update Makefile.bsd-wrapper
tweak openbsd hints file for arm and m68k

merge local changes into perl-5.8.3

Resolve conflicts for perl 5.8.2, remove old files, and add OpenBSD-specific scaffolding

Resolve conflicts, remove old files, merge local changes

merge in perl 5.6.1 with our local changes

perl-5.6.0 + local changes

perl5.005_03 (stock)

perl 5.004_04

branches: 1.1.1;
Initial revision

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

Timing is good deraadt@, OK sthen@

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, 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@

Update to perl 5.20.3

OK bluhm@

branches: 1.18.4; 1.18.6;
Fix merge conflicts, remove extra files, match upstream perl-5.20.1

ok deraadt@ sthen@ espie@ miod@

Merge perl-5.18.2 plus local patches, remove old files

OK espie@ sthen@ deraadt@

merge/resolve conflicts
(some more to do after this one)

merge in perl 5.12.2 plus local changes

Merge in some local changes that got lost.

Merge in perl 5.10.1

fix conflicts and merge in local changes to perl 5.10.0

merge in perl 5.8.8

sync in-tree perl with 5.8.6

merge 5.8.5 into HEAD
remove now-unused files
crank libperl shared library major number
update Makefile.bsd-wrapper
tweak openbsd hints file for arm and m68k

merge local changes into perl-5.8.3

Resolve conflicts for perl 5.8.2, remove old files, and add OpenBSD-specific scaffolding

Resolve conflicts, remove old files, merge local changes

merge in perl 5.6.1 with our local changes

perl-5.6.0 + local changes

perl5.005_03 (stock)

perl 5.004_04

branches: 1.1.1;
Initial revision

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, 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@

Update to perl 5.20.3

OK bluhm@

branches: 1.18.4; 1.18.6;
Fix merge conflicts, remove extra files, match upstream perl-5.20.1

ok deraadt@ sthen@ espie@ miod@

Merge perl-5.18.2 plus local patches, remove old files

OK espie@ sthen@ deraadt@

merge/resolve conflicts
(some more to do after this one)

merge in perl 5.12.2 plus local changes

Merge in some local changes that got lost.

Merge in perl 5.10.1

fix conflicts and merge in local changes to perl 5.10.0

merge in perl 5.8.8

sync in-tree perl with 5.8.6

merge 5.8.5 into HEAD
remove now-unused files
crank libperl shared library major number
update Makefile.bsd-wrapper
tweak openbsd hints file for arm and m68k

merge local changes into perl-5.8.3

Resolve conflicts for perl 5.8.2, remove old files, and add OpenBSD-specific scaffolding

Resolve conflicts, remove old files, merge local changes

merge in perl 5.6.1 with our local changes

perl-5.6.0 + local changes

perl5.005_03 (stock)

perl 5.004_04

branches: 1.1.1;
Initial revision

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, 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@

Update to perl 5.20.3

OK bluhm@

branches: 1.18.4; 1.18.6;
Fix merge conflicts, remove extra files, match upstream perl-5.20.1

ok deraadt@ sthen@ espie@ miod@

Merge perl-5.18.2 plus local patches, remove old files

OK espie@ sthen@ deraadt@

merge/resolve conflicts
(some more to do after this one)

merge in perl 5.12.2 plus local changes

Merge in some local changes that got lost.

Merge in perl 5.10.1

fix conflicts and merge in local changes to perl 5.10.0

merge in perl 5.8.8

sync in-tree perl with 5.8.6

merge 5.8.5 into HEAD
remove now-unused files
crank libperl shared library major number
update Makefile.bsd-wrapper
tweak openbsd hints file for arm and m68k

merge local changes into perl-5.8.3

Resolve conflicts for perl 5.8.2, remove old files, and add OpenBSD-specific scaffolding

Resolve conflicts, remove old files, merge local changes

merge in perl 5.6.1 with our local changes

perl-5.6.0 + local changes

perl5.005_03 (stock)

perl 5.004_04

branches: 1.1.1;
Initial revision