From 948b8455fc647be39caf4e50155b42e5dac1b561 Mon Sep 17 00:00:00 2001 From: Father Chrysostomos Date: Mon, 14 Mar 2011 14:06:03 -0700 Subject: [PATCH] perldelta: Clean up the Security section --- pod/perldelta.pod | 17 ++++++----------- 1 file changed, 6 insertions(+), 11 deletions(-) diff --git a/pod/perldelta.pod b/pod/perldelta.pod index 8984f8d..4dc8b76 100644 --- a/pod/perldelta.pod +++ b/pod/perldelta.pod @@ -455,21 +455,16 @@ DTrace will print: =head1 Security -=head2 Restrict \p{IsUserDefined} to In\w+ and Is\w+ +=head2 User-defined regular expression properties In L, it says you can create custom properties by defining subroutines whose names begin with -"In" or "Is". However, perl doesn't actually enforce that naming -restriction, so \p{foo::bar} will call foo::Bar() if it exists. - -This commit finally enforces this convention. Note that this broke a -number of existing tests for properties, since they didn't always use an -Is/In prefix. - -=head2 User-defined regular expression properties +"In" or "Is". However, Perl did not actually enforce that naming +restriction, so \p{foo::bar} could call foo::bar() if it existed. Now this +convention has been enforced. -Perl no longer allows a tainted regular expression to invoke a user-defined -property via C<\p{...}> syntax. It simply dies instead [perl #82616]. +Also, Perl no longer allows a tainted regular expression to invoke a +user-defined. It simply dies instead [perl #82616]. =head1 Incompatible Changes -- 1.8.3.1