Re: [AppDb] [2/3] safe functions

2006-06-26 Thread Chris Morgan
On Monday 26 June 2006 12:29 pm, Jonathan Ernst wrote: > Le lundi 26 juin 2006 à 11:54 -0400, Chris Morgan a écrit : > > [...] > > The most effective solution involves both filtering and sql protection. > > The first layer of protection is to filter each input variable down to > > the most restric

Re: [AppDb] [2/3] safe functions

2006-06-26 Thread Jonathan Ernst
Le lundi 26 juin 2006 à 11:54 -0400, Chris Morgan a écrit : > [...] > The most effective solution involves both filtering and sql protection. The > first layer of protection is to filter each input variable down to the most > restrictive data we can accept. > > The next step is to ensure that e

Re: [AppDb] [2/3] safe functions

2006-06-26 Thread Chris Morgan
On Monday 26 June 2006 1:50 am, Jonathan Ernst wrote: > Le dimanche 25 juin 2006 à 20:00 -0400, Chris Morgan a écrit : > > Hi Jonathan. > > > > You'll want to talk to EA about the filtering changes. The plan is to > > filter using the same syntax and flags that the php filter extension > > is goin

Re: [AppDb] [2/3] safe functions

2006-06-25 Thread Jonathan Ernst
Le dimanche 25 juin 2006 à 20:00 -0400, Chris Morgan a écrit : > Hi Jonathan. > > You'll want to talk to EA about the filtering changes. The plan is to > filter using the same syntax and flags that the php filter extension > is going to use so we can easily switch over to this extension in the >

Re: [AppDb] [2/3] safe functions

2006-06-25 Thread Chris Morgan
Hi Jonathan. You'll want to talk to EA about the filtering changes. The plan is to filter using the same syntax and flags that the php filter extension is going to use so we can easily switch over to this extension in the future. Also, I've submitted a patch for review to [EMAIL PROTECTED] and