On Fri, Feb 19, 2010 at 09:00:59AM -0800, David E. Wheeler wrote: > On Feb 19, 2010, at 1:13 AM, Tim Bunce wrote: > > >> Hrm. I don't have this bug with Safe 3.19, FWIW. > > > > That's because Safe 1.19 (which I presume you meant) doesn't execute > > closures 'inside' the Safe compartment. So when the regex executes at > > runtime the C code looks up the utf8::SWASHNEW method without a problem. > > Oh, so 2.19 is less secure in that regard, yes?
Yes. When code that was compiled outside the compartment is executed by a plperl function, including internal regex implementation code, that code could call eval/require/do etc. and the newly compiled code wouldn't have any restrictions. With Safe 2.20+ the newly compiled code is subject to the same restrictions as plperl. So what we're seeing is the knock-on effects of that tighting of security. That's why I'd rather move forward rather than back (though there have been times over the last 48 hours where moving back to Safe 1.19 looked very appealing :) Tim. -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
