[Esapi-user] [Esapi-dev] Regarding ESAPI WAF
augustd at codemagi.com
Thu Nov 18 20:32:42 EST 2010
Log4J could still be a dependency if you use the ESAPI logger...
On Tue, Nov 16, 2010 at 3:20 AM, Jim Manico <jim.manico at owasp.org> wrote:
> +1 remove
> -Jim Manico
> On Nov 15, 2010, at 6:50 PM, "Kevin W. Wall" <kevin.w.wall at gmail.com>
> > On 11/15/2010 11:34 PM, Chris Schmidt wrote:
> >> I am forwarding this message along for Arshan
> >> ---
> >> Devs and users,
> >> For the final 2.0 release we wanted to more tightly integrate the WAF
> >> the rest of ESAPI. This means that the WAF will use the ESAPI logger
> >> of log4j, its exceptions will extend ESAPI exceptions, etc. Does anyone
> >> object to these old API being removed instead of deprecated? The reason
> >> like to remove entirely as opposed to deprecate is to remove
> dependencies on
> >> things like log4j which would otherwise hang around only to satisfy the
> >> deprecated methods.
> >> Looking for your vote on this - remove or deprecate?
> >> Arshan
> > +1 for burning it to the ground (i.e., removal)
> > --
> > Kevin W. Wall
> > "The most likely way for the world to be destroyed, most experts agree,
> > is by accident. That's where we come in; we're computer professionals.
> > We cause accidents." -- Nathaniel Borenstein, co-creator of MIME
> > _______________________________________________
> > Esapi-user mailing list
> > Esapi-user at lists.owasp.org
> > https://lists.owasp.org/mailman/listinfo/esapi-user
> Esapi-dev mailing list
> Esapi-dev at lists.owasp.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Esapi-user