[OWASP-ESAPI] ESAPI vs Other OWASP Projects
jeff.williams at owasp.org
Mon May 18 17:56:33 EDT 2009
For the most part, ESAPI has re-engineered (and improved) the work from
those other projects. The exception is AntiSamy, where ESAPI provides a
simple interface to the powerful library. We're looking at absorbing
CSRFGuard into ESAPI, but we don't have a defined schedule.
Jeff Williams, Chair
The OWASP Foundation
> -----Original Message-----
> From: owasp-esapi-bounces at lists.owasp.org [mailto:owasp-esapi-
> bounces at lists.owasp.org] On Behalf Of Steve Wakefield
> Sent: Sunday, May 17, 2009 9:31 PM
> To: owasp-esapi at lists.owasp.org
> Subject: [OWASP-ESAPI] ESAPI vs Other OWASP Projects
> I have a general question about the ESAPI project and how it relates to
> other OWASP projects such as Stinger and CSRFGuard.
> Does ESAPI include the full code base of the other OWASP projects, and
> just provide a wrapper around them to provide integration, or are they
> completely different applications?
> Disclaimer Notice
> This message contains privileged and confidential information intended
> only for the use of the addressee named above. If you are not the
> intended recipient of this message you are hereby notified that you
> must not disseminate, copy or take any action or place any reliance on
> it. If you have received this message in error please notify Ultradata
> immediately on +61 3 9291 1600. Any views expressed in this message are
> those of the individual sender, except where the sender specifically
> states them to be the views of Ultradata Australia Pty. Ltd.
> To unsubscribe from receiving commercial electronic messages from
> Ultradata Australia please email unsubscribe at ultradata.com.au with the
> subject heading "Unsubscribe".
> OWASP-ESAPI mailing list
> OWASP-ESAPI at lists.owasp.org
More information about the OWASP-ESAPI