diff options
Diffstat (limited to 'upstream/archlinux/man1/perl5263delta.1perl')
| -rw-r--r-- | upstream/archlinux/man1/perl5263delta.1perl | 228 |
1 files changed, 228 insertions, 0 deletions
diff --git a/upstream/archlinux/man1/perl5263delta.1perl b/upstream/archlinux/man1/perl5263delta.1perl new file mode 100644 index 00000000..2a6bc014 --- /dev/null +++ b/upstream/archlinux/man1/perl5263delta.1perl @@ -0,0 +1,228 @@ +.\" -*- mode: troff; coding: utf-8 -*- +.\" Automatically generated by Pod::Man 5.01 (Pod::Simple 3.43) +.\" +.\" Standard preamble: +.\" ======================================================================== +.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 +.. +.\" \*(C` and \*(C' are quotes in nroff, nothing in troff, for use with C<>. +.ie n \{\ +. ds C` "" +. ds C' "" +'br\} +.el\{\ +. ds C` +. ds C' +'br\} +.\" +.\" Escape single quotes in literal strings from groff's Unicode transform. +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" +.\" If the F register is >0, we'll generate index entries on stderr for +.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index +.\" entries marked with X<> in POD. Of course, you'll have to process the +.\" output yourself in some meaningful fashion. +.\" +.\" Avoid warning from groff about undefined register 'F'. +.de IX +.. +.nr rF 0 +.if \n(.g .if rF .nr rF 1 +.if (\n(rF:(\n(.g==0)) \{\ +. if \nF \{\ +. de IX +. tm Index:\\$1\t\\n%\t"\\$2" +.. +. if !\nF==2 \{\ +. nr % 0 +. nr F 2 +. \} +. \} +.\} +.rr rF +.\" ======================================================================== +.\" +.IX Title "PERL5263DELTA 1perl" +.TH PERL5263DELTA 1perl 2024-02-11 "perl v5.38.2" "Perl Programmers Reference Guide" +.\" For nroff, turn off justification. Always turn off hyphenation; it makes +.\" way too many mistakes in technical documents. +.if n .ad l +.nh +.SH NAME +perl5263delta \- what is new for perl v5.26.3 +.SH DESCRIPTION +.IX Header "DESCRIPTION" +This document describes differences between the 5.26.2 release and the 5.26.3 +release. +.PP +If you are upgrading from an earlier release such as 5.26.1, first read +perl5262delta, which describes differences between 5.26.1 and 5.26.2. +.SH Security +.IX Header "Security" +.SS "[CVE\-2018\-12015] Directory traversal in module Archive::Tar" +.IX Subsection "[CVE-2018-12015] Directory traversal in module Archive::Tar" +By default, Archive::Tar doesn't allow extracting files outside the current +working directory. However, this secure extraction mode could be bypassed by +putting a symlink and a regular file with the same name into the tar file. +.PP +[GH #16580] <https://github.com/Perl/perl5/issues/16580> +[cpan #125523] <https://rt.cpan.org/Ticket/Display.html?id=125523> +.SS "[CVE\-2018\-18311] Integer overflow leading to buffer overflow and segmentation fault" +.IX Subsection "[CVE-2018-18311] Integer overflow leading to buffer overflow and segmentation fault" +Integer arithmetic in \f(CWPerl_my_setenv()\fR could wrap when the combined length +of the environment variable name and value exceeded around 0x7fffffff. This +could lead to writing beyond the end of an allocated buffer with attacker +supplied data. +.PP +[GH #16560] <https://github.com/Perl/perl5/issues/16560> +.SS "[CVE\-2018\-18312] Heap-buffer-overflow write in S_regatom (regcomp.c)" +.IX Subsection "[CVE-2018-18312] Heap-buffer-overflow write in S_regatom (regcomp.c)" +A crafted regular expression could cause heap-buffer-overflow write during +compilation, potentially allowing arbitrary code execution. +.PP +[GH #16649] <https://github.com/Perl/perl5/issues/16649> +.SS "[CVE\-2018\-18313] Heap-buffer-overflow read in S_grok_bslash_N (regcomp.c)" +.IX Subsection "[CVE-2018-18313] Heap-buffer-overflow read in S_grok_bslash_N (regcomp.c)" +A crafted regular expression could cause heap-buffer-overflow read during +compilation, potentially leading to sensitive information being leaked. +.PP +[GH #16554] <https://github.com/Perl/perl5/issues/16554> +.SS "[CVE\-2018\-18314] Heap-buffer-overflow write in S_regatom (regcomp.c)" +.IX Subsection "[CVE-2018-18314] Heap-buffer-overflow write in S_regatom (regcomp.c)" +A crafted regular expression could cause heap-buffer-overflow write during +compilation, potentially allowing arbitrary code execution. +.PP +[GH #16041] <https://github.com/Perl/perl5/issues/16041> +.SH "Incompatible Changes" +.IX Header "Incompatible Changes" +There are no changes intentionally incompatible with 5.26.2. If any exist, +they are bugs, and we request that you submit a report. See +"Reporting Bugs" below. +.SH "Modules and Pragmata" +.IX Header "Modules and Pragmata" +.SS "Updated Modules and Pragmata" +.IX Subsection "Updated Modules and Pragmata" +.IP \(bu 4 +Archive::Tar has been upgraded from version 2.24 to 2.24_01. +.IP \(bu 4 +Module::CoreList has been upgraded from version 5.20180414_26 to 5.20181129_26. +.SH Diagnostics +.IX Header "Diagnostics" +The following additions or changes have been made to diagnostic output, +including warnings and fatal error messages. For the complete list of +diagnostic messages, see perldiag. +.SS "New Diagnostics" +.IX Subsection "New Diagnostics" +\fINew Errors\fR +.IX Subsection "New Errors" +.IP \(bu 4 +Unexpected ']' with no following ')' in (?[... in regex; marked by <\-\- HERE in m/%s/ +.Sp +(F) While parsing an extended character class a ']' character was encountered +at a point in the definition where the only legal use of ']' is to close the +character class definition as part of a '])', you may have forgotten the close +paren, or otherwise confused the parser. +.IP \(bu 4 +Expecting close paren for nested extended charclass in regex; marked by <\-\- HERE in m/%s/ +.Sp +(F) While parsing a nested extended character class like: +.Sp +.Vb 2 +\& (?[ ... (?flags:(?[ ... ])) ... ]) +\& ^ +.Ve +.Sp +we expected to see a close paren ')' (marked by ^) but did not. +.IP \(bu 4 +Expecting close paren for wrapper for nested extended charclass in regex; marked by <\-\- HERE in m/%s/ +.Sp +(F) While parsing a nested extended character class like: +.Sp +.Vb 2 +\& (?[ ... (?flags:(?[ ... ])) ... ]) +\& ^ +.Ve +.Sp +we expected to see a close paren ')' (marked by ^) but did not. +.SS "Changes to Existing Diagnostics" +.IX Subsection "Changes to Existing Diagnostics" +.IP \(bu 4 +Syntax error in (?[...]) in regex; marked by <\-\- HERE in m/%s/ +.Sp +This fatal error message has been slightly expanded (from "Syntax error in +(?[...]) in regex m/%s/") for greater clarity. +.SH Acknowledgements +.IX Header "Acknowledgements" +Perl 5.26.3 represents approximately 8 months of development since Perl 5.26.2 +and contains approximately 4,500 lines of changes across 51 files from 15 +authors. +.PP +Excluding auto-generated files, documentation and release tools, there were +approximately 770 lines of changes to 10 .pm, .t, .c and .h files. +.PP +Perl continues to flourish into its third decade thanks to a vibrant community +of users and developers. The following people are known to have contributed +the improvements that became Perl 5.26.3: +.PP +Aaron Crane, Abigail, Chris 'BinGOs' Williams, Dagfinn Ilmari Mannsåker, David +Mitchell, H.Merijn Brand, James E Keenan, John SJ Anderson, Karen Etheridge, +Karl Williamson, Sawyer X, Steve Hay, Todd Rinaldo, Tony Cook, Yves Orton. +.PP +The list above is almost certainly incomplete as it is automatically generated +from version control history. In particular, it does not include the names of +the (very much appreciated) contributors who reported issues to the Perl bug +tracker. +.PP +Many of the changes included in this version originated in the CPAN modules +included in Perl's core. We're grateful to the entire CPAN community for +helping Perl to flourish. +.PP +For a more complete list of all of Perl's historical contributors, please see +the \fIAUTHORS\fR file in the Perl source distribution. +.SH "Reporting Bugs" +.IX Header "Reporting Bugs" +If you find what you think is a bug, you might check the perl bug database +at <https://rt.perl.org/> . There may also be information at +<http://www.perl.org/> , the Perl Home Page. +.PP +If you believe you have an unreported bug, please run the perlbug program +included with your release. Be sure to trim your bug down to a tiny but +sufficient test case. Your bug report, along with the output of \f(CW\*(C`perl \-V\*(C'\fR, +will be sent off to perlbug@perl.org to be analysed by the Perl porting team. +.PP +If the bug you are reporting has security implications which make it +inappropriate to send to a publicly archived mailing list, then see +"SECURITY VULNERABILITY CONTACT INFORMATION" in perlsec +for details of how to report the issue. +.SH "Give Thanks" +.IX Header "Give Thanks" +If you wish to thank the Perl 5 Porters for the work we had done in Perl 5, +you can do so by running the \f(CW\*(C`perlthanks\*(C'\fR program: +.PP +.Vb 1 +\& perlthanks +.Ve +.PP +This will send an email to the Perl 5 Porters list with your show of thanks. +.SH "SEE ALSO" +.IX Header "SEE ALSO" +The \fIChanges\fR file for an explanation of how to view exhaustive details on +what changed. +.PP +The \fIINSTALL\fR file for how to build Perl. +.PP +The \fIREADME\fR file for general stuff. +.PP +The \fIArtistic\fR and \fICopying\fR files for copyright information. |