Re: [PHP-DEV] taint as a first-class feature for php 7.1

2015-11-19 Thread Stanislav Malyshev
Hi! > I’m requesting that the functions taint() and untaint() as well as > the ability to log taint information be available in the standard > interpreter without extensions. Given that this feature has performance implications, and not universally needed, I don't think this would be a good idea.

Re: [PHP-DEV] taint as a first-class feature for php 7.1

2015-11-19 Thread François Laupretre
Le 19/11/2015 04:52, Christopher Owen a écrit : I’m requesting that the functions taint() and untaint() as well as the ability to log taint information be available in the standard interpreter without extensions. Christopher Owen. On Nov 18, 2015, at 8:26 PM, Stanislav Malyshev wrote:

Re: [PHP-DEV] taint as a first-class feature for php 7.1

2015-11-18 Thread Christopher Owen
I’m requesting that the functions taint() and untaint() as well as the ability to log taint information be available in the standard interpreter without extensions. Christopher Owen. > On Nov 18, 2015, at 8:26 PM, Stanislav Malyshev wrote: > > Hi! > >> As discussion seems to have died out,

Re: [PHP-DEV] taint as a first-class feature for php 7.1

2015-11-18 Thread Stanislav Malyshev
Hi! > As discussion seems to have died out, I would like to propose moving > to the next stage for inclusion of taint as a first class feature of > php 7.1. What is the difference between what exists now (i.e., extension) and what you seek to do in 7.1? What do you mean by "first class feature"?

Re: [PHP-DEV] taint as a first-class feature for php 7.1

2015-11-17 Thread Lester Caine
On 17/11/15 07:34, Christopher Owen wrote: > - Including taint as a first class feature will allow for it to be available > in future linux distribution packages of php Any decent linux distribution already makes 'optional' extensions easy to switch on or off. What you are actually proposing by m