diff options
Diffstat (limited to 'upstream/debian-bookworm/man1/perl5244delta.1')
| -rw-r--r-- | upstream/debian-bookworm/man1/perl5244delta.1 | 182 |
1 files changed, 182 insertions, 0 deletions
diff --git a/upstream/debian-bookworm/man1/perl5244delta.1 b/upstream/debian-bookworm/man1/perl5244delta.1 new file mode 100644 index 00000000..3646a5c2 --- /dev/null +++ b/upstream/debian-bookworm/man1/perl5244delta.1 @@ -0,0 +1,182 @@ +.\" Automatically generated by Pod::Man 4.14 (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 +.. +.\" 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. \*(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- +.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" '' +. 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 "PERL5244DELTA 1" +.TH PERL5244DELTA 1 "2023-11-25" "perl v5.36.0" "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" +perl5244delta \- what is new for perl v5.24.4 +.SH "DESCRIPTION" +.IX Header "DESCRIPTION" +This document describes differences between the 5.24.3 release and the 5.24.4 +release. +.PP +If you are upgrading from an earlier release such as 5.24.2, first read +perl5243delta, which describes differences between 5.24.2 and 5.24.3. +.SH "Security" +.IX Header "Security" +.SS "[\s-1CVE\-2018\-6797\s0] heap-buffer-overflow (\s-1WRITE\s0 of size 1) in S_regatom (regcomp.c)" +.IX Subsection "[CVE-2018-6797] heap-buffer-overflow (WRITE of size 1) in S_regatom (regcomp.c)" +A crafted regular expression could cause a heap buffer write overflow, with +control over the bytes written. +[\s-1GH\s0 #16185] <https://github.com/Perl/perl5/issues/16185> +.SS "[\s-1CVE\-2018\-6798\s0] Heap-buffer-overflow in Perl_\|_byte_dump_string (utf8.c)" +.IX Subsection "[CVE-2018-6798] Heap-buffer-overflow in Perl__byte_dump_string (utf8.c)" +Matching a crafted locale dependent regular expression could cause a heap +buffer read overflow and potentially information disclosure. +[\s-1GH\s0 #16143] <https://github.com/Perl/perl5/issues/16143> +.SS "[\s-1CVE\-2018\-6913\s0] heap-buffer-overflow in S_pack_rec" +.IX Subsection "[CVE-2018-6913] heap-buffer-overflow in S_pack_rec" +\&\f(CW\*(C`pack()\*(C'\fR could cause a heap buffer write overflow with a large item count. +[\s-1GH\s0 #16098] <https://github.com/Perl/perl5/issues/16098> +.SS "Assertion failure in Perl_\|_core_swash_init (utf8.c)" +.IX Subsection "Assertion failure in Perl__core_swash_init (utf8.c)" +Control characters in a supposed Unicode property name could cause perl to +crash. This has been fixed. +[perl #132055] <https://rt.perl.org/Public/Bug/Display.html?id=132055> +[perl #132553] <https://rt.perl.org/Public/Bug/Display.html?id=132553> +[perl #132658] <https://rt.perl.org/Public/Bug/Display.html?id=132658> +.SH "Incompatible Changes" +.IX Header "Incompatible Changes" +There are no changes intentionally incompatible with 5.24.3. If any exist, +they are bugs, and we request that you submit a report. See \*(L"Reporting +Bugs\*(R" below. +.SH "Modules and Pragmata" +.IX Header "Modules and Pragmata" +.SS "Updated Modules and Pragmata" +.IX Subsection "Updated Modules and Pragmata" +.IP "\(bu" 4 +Module::CoreList has been upgraded from version 5.20170922_24 to 5.20180414_24. +.SH "Selected Bug Fixes" +.IX Header "Selected Bug Fixes" +.IP "\(bu" 4 +The \f(CW\*(C`readpipe()\*(C'\fR built-in function now checks at compile time that it has only +one parameter expression, and puts it in scalar context, thus ensuring that it +doesn't corrupt the stack at runtime. +[\s-1GH\s0 #2793] <https://github.com/Perl/perl5/issues/2793> +.SH "Acknowledgements" +.IX Header "Acknowledgements" +Perl 5.24.4 represents approximately 7 months of development since Perl 5.24.3 +and contains approximately 2,400 lines of changes across 49 files from 12 +authors. +.PP +Excluding auto-generated files, documentation and release tools, there were +approximately 1,300 lines of changes to 12 .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.24.4: +.PP +Abigail, Chris 'BinGOs' Williams, John \s-1SJ\s0 Anderson, Karen Etheridge, Karl +Williamson, Renee Baecker, Sawyer X, Steve Hay, Todd Rinaldo, Tony Cook, Yves +Orton, Zefram. +.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 \s-1CPAN\s0 modules +included in Perl's core. We're grateful to the entire \s-1CPAN\s0 community for +helping Perl to flourish. +.PP +For a more complete list of all of Perl's historical contributors, please see +the \fI\s-1AUTHORS\s0\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 articles recently +posted to the comp.lang.perl.misc newsgroup and 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 +\&\*(L"\s-1SECURITY VULNERABILITY CONTACT INFORMATION\*(R"\s0 in perlsec +for details of how to report the issue. +.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 \fI\s-1INSTALL\s0\fR file for how to build Perl. +.PP +The \fI\s-1README\s0\fR file for general stuff. +.PP +The \fIArtistic\fR and \fICopying\fR files for copyright information. |