|
NAMEperl5142delta - what is new for perl v5.14.2DESCRIPTIONThis document describes differences between the 5.14.1 release and the 5.14.2 release.If you are upgrading from an earlier release such as 5.14.0, first read perl5141delta, which describes differences between 5.14.0 and 5.14.1. Core EnhancementsNo changes since 5.14.0.Security"File::Glob::bsd_glob()" memory error with GLOB_ALTDIRFUNC (CVE-2011-2728).Calling "File::Glob::bsd_glob" with the unsupported flag GLOB_ALTDIRFUNC would cause an access violation / segfault. A Perl program that accepts a flags value from an external source could expose itself to denial of service or arbitrary code execution attacks. There are no known exploits in the wild. The problem has been corrected by explicitly disabling all unsupported flags and setting unused function pointers to null. Bug reported by Clement Lecigne."Encode" decode_xs n-byte heap-overflow (CVE-2011-2939)A bug in "Encode" could, on certain inputs, cause the heap to overflow. This problem has been corrected. Bug reported by Robert Zacek.Incompatible ChangesThere are no changes intentionally incompatible with 5.14.0. If any exist, they are bugs and reports are welcome.DeprecationsThere have been no deprecations since 5.14.0.Modules and PragmataNew Modules and PragmataNoneUpdated Modules and Pragmata
Removed Modules and PragmataNonePlatform SupportNew PlatformsNoneDiscontinued PlatformsNonePlatform-Specific Notes
Bug Fixes
Known ProblemsThis is a list of some significant unfixed bugs, which are regressions from 5.12.0.
AcknowledgementsPerl 5.14.2 represents approximately three months of development since Perl 5.14.1 and contains approximately 1200 lines of changes across 61 files from 9 authors.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.14.2: Craig A. Berry, David Golden, Father Chrysostomos, Florian Ragwitz, H.Merijn Brand, Karl Williamson, Nicholas Clark, Pau Amma and Ricardo Signes. Reporting BugsIf 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 http://rt.perl.org/perlbug/ . There may also be information at http://www.perl.org/ , the Perl Home Page.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 "perl -V", will be sent off to perlbug@perl.org to be analysed by the Perl porting team. If the bug you are reporting has security implications, which make it inappropriate to send to a publicly archived mailing list, then please send it to perl5-security-report@perl.org. This points to a closed subscription unarchived mailing list, which includes all the core committers, who be able to help assess the impact of issues, figure out a resolution, and help co-ordinate the release of patches to mitigate or fix the problem across all platforms on which Perl is supported. Please only use this address for security issues in the Perl core, not for modules independently distributed on CPAN. SEE ALSOThe Changes file for an explanation of how to view exhaustive details on what changed.The INSTALL file for how to build Perl. The README file for general stuff. The Artistic and Copying files for copyright information.
Visit the GSP FreeBSD Man Page Interface. |