> With the caveat that I read the list, but have not worked with many of the
features I read about,
> wouldn't it be posible to create a set of Input Modules to do validation?
I recall a discussion
> about having input modules be able to wrap other input modules, so you
should simply be able to
> a
With the caveat that I read the list, but have not worked with many of the features I
read about,
wouldn't it be posible to create a set of Input Modules to do validation? I recall a
discussion
about having input modules be able to wrap other input modules, so you should simply
be able to
acces
>> 4. Some users don't want additional protection. They are happy with the
>> current level of (lack of) protection, and add their own as needed.
(Peter
>> Hunsberger)
>
> AFAIU some would also like to have a centralized management...
What I'd really like to see is a good general infrastructure w
On 06.Nov.2002 -- 01:47 AM, Torsten Curdt wrote:
> On Wed, 2002-11-06 at 01:00, Carl Mäsak wrote:
> > 6. There doesn't seem to be any explicit mention of SQL Injections in the
> > Cocoon docs. (Torsten Cordt)
>
> Christian, did you check the docs?
Yes -- and have added three paragraphs. They are
--- Torsten Curdt <[EMAIL PROTECTED]> wrote:
> On Wed, 2002-11-06 at 01:00, Carl Mäsak wrote:
> > These are a few things in the "SQL Injection"
> thread that ring true to me
> > (I here take the liberty of rephrasing people's
> opinions in my own words,
> > but try to give due credit to the first
On Wed, 2002-11-06 at 01:00, Carl Mäsak wrote:
> These are a few things in the "SQL Injection" thread that ring true to me
> (I here take the liberty of rephrasing people's opinions in my own words,
> but try to give due credit to the first one to bring up each topic):
>
> 1. Functionality for ma
