diff options
author | Andrew Fresh <afresh1@cvs.openbsd.org> | 2021-03-01 23:16:25 +0000 |
---|---|---|
committer | Andrew Fresh <afresh1@cvs.openbsd.org> | 2021-03-01 23:16:25 +0000 |
commit | 830521676276b6133a5cd5127f3cc42f5590917a (patch) | |
tree | 22da143436a967a55d784f6ed8cf24cbffaf3927 /gnu/usr.bin/perl/Porting | |
parent | 161ccc0397268d5c7bfa259e56c00df5595df138 (diff) |
Import perl-5.32.1
OK sthen@
Diffstat (limited to 'gnu/usr.bin/perl/Porting')
-rw-r--r-- | gnu/usr.bin/perl/Porting/README.y2038 | 2 | ||||
-rw-r--r-- | gnu/usr.bin/perl/Porting/exercise_makedef.pl | 4 | ||||
-rw-r--r-- | gnu/usr.bin/perl/Porting/manicheck | 4 | ||||
-rw-r--r-- | gnu/usr.bin/perl/Porting/security_template.pod | 83 |
4 files changed, 90 insertions, 3 deletions
diff --git a/gnu/usr.bin/perl/Porting/README.y2038 b/gnu/usr.bin/perl/Porting/README.y2038 index 0e83775cf32..c29f336d1b4 100644 --- a/gnu/usr.bin/perl/Porting/README.y2038 +++ b/gnu/usr.bin/perl/Porting/README.y2038 @@ -2,7 +2,7 @@ The y2038 implementation for perl =========================================================================== This is an implementation of POSIX time.h which solves the year 2038 bug on systems where time_t is only 32 bits. It is implemented in bog-standard -ANSI C. The latest version can be found at http://y2038.googlecode.com/ +ANSI C. The latest version can be found at https://github.com/evalEmpire/y2038 It makes use of the system's native 32 bit functions to perform time zone and daylight savings time calculations and thus does *not* need to ship its diff --git a/gnu/usr.bin/perl/Porting/exercise_makedef.pl b/gnu/usr.bin/perl/Porting/exercise_makedef.pl index 4003410ba09..3b2d1b3512a 100644 --- a/gnu/usr.bin/perl/Porting/exercise_makedef.pl +++ b/gnu/usr.bin/perl/Porting/exercise_makedef.pl @@ -48,11 +48,11 @@ $SIG{INT} = sub { die }; # Trigger END processing close $out or die "Can't close $mpm: $!"; } -my @args = (platform => [map {"PLATFORM=$_"} qw(aix win32 wince os2 netware vms test)], +my @args = (platform => [map {"PLATFORM=$_"} qw(aix win32 os2 netware vms test)], cflags => ['', 'CCFLAGS=-Dperl=rules -Dzzz'], Deq => ['', '-Dbeer=foamy'], D => ['', '-DPERL_IMPLICIT_SYS'], - cctype => ['', map {"CCTYPE=$_"} qw (MSVC60 GCC)], + cctype => ['', 'CCTYPE=GCC'], filetype => ['', 'FILETYPE=def', 'FILETYPE=imp'], targ_dir => ['', 'TARG_DIR=t/../'], ); diff --git a/gnu/usr.bin/perl/Porting/manicheck b/gnu/usr.bin/perl/Porting/manicheck index b544a12252f..47bb2df381c 100644 --- a/gnu/usr.bin/perl/Porting/manicheck +++ b/gnu/usr.bin/perl/Porting/manicheck @@ -19,8 +19,12 @@ find { wanted => sub { my $x = $File::Find::name; $x =~ s/^..//; return if -d; + return if $_ eq '.mailmap'; return if $_ eq '.gitignore'; + return if $_ eq '.gitattributes'; + return if $_ eq '.git_patch'; return if $x =~ /^\.git\b/; + return if $x =~ m{^\.github/}; print "$x\t\tnot in MANIFEST\n" if !$files{$x}; }, }, "."; diff --git a/gnu/usr.bin/perl/Porting/security_template.pod b/gnu/usr.bin/perl/Porting/security_template.pod new file mode 100644 index 00000000000..62334274e85 --- /dev/null +++ b/gnu/usr.bin/perl/Porting/security_template.pod @@ -0,0 +1,83 @@ +=begin editor + +Delete this begin/end block before publication. + +Not every heading below is appropriate for every security issue, so +some may be deleted. + +Look for FIXME to see what needs to be filled in. + +=end editor + +=encoding utf8 + +=head1 NAME + +FIXME - short description of the security issue, with an identifier of the issue as the manpage name + +=head1 DESCRIPTION + +=for editor +Ideally, FIXME here should be the CVE-ID as a link to cve.mitre.org + +This document describes the +L<FIXME|http://cve.mitre.org/cgi-bin/cvename.cgi?name=FIXME> +security vulnerability for perl 5. + +=head2 Are there any known exploits "in the wild" for this vulnerability + +FIXME or delete + +=head2 Who is particularly vulnerable because of this issue? + +FIXME or delete + +=head2 What is the nature of the vulnerability? + +FIXME + +=head2 What potential exploits are enabled by this vulnerability? + +FIXME or delete + +=head2 Which major versions of perl 5 are affected? + +FIXME with a list of versions that are affected, and which were updated. + +=head2 How can users protect themselves? + +FIXME or use the following: + +If you are vulnerable, upgrade to the latest maintenance release for the +version of perl you are using. + +If your release of perl is no longer supported by the perl 5 committers you +may need to upgrade to a new major release of perl. The versions currently +supported by the perl 5 committers are +FIXME 5.28.2 (until 2020-05-31) +and +FIXME 5.30.1 (until 2021-05-31). +The current version of perl is available from https://www.perl.org/get.html . + +=head2 Who was given access to the information about the vulnerability? + +FIXME or use the following: + +Specifics about the vulnerability were first disclosed to +C<perl-security>, a closed subscriber mailing list that has a +subset of the perl committers subcribed to it. + +=head2 When was the vulnerability discovered? + +FIXME + +=head2 Who discovered the vulnerability? + +FIXME + +=head2 How was the vulnerability reported? + +FIXME: something like "So-and-so sent email to +perl-security@perl.org" + +=cut |