[owasp-antisamy] Hey list - How to install antisamy .net
troy.doty at touchnet.com
Wed Oct 3 14:42:13 UTC 2012
According to a previous correspondence on this mailing list, antisamy was superseded by another .NET library.
That is correct - the .NET version is not actively being maintained,
mainly because the antixss library functionality supersedes that of
I know this doesn't answer your question, but perhaps you can take this to your boss and convince him it was his idea. Otherwise, perhaps Jerry (or someone else on that thread) can help you out.
From: owasp-antisamy-bounces at lists.owasp.org [mailto:owasp-antisamy-bounces at lists.owasp.org] On Behalf Of Eric Schultz
Sent: Wednesday, October 03, 2012 9:04 AM
To: owasp-antisamy at lists.owasp.org
Subject: [owasp-antisamy] Hey list - How to install antisamy .net
My manager must have invented a time traveling device, as he just gave me a 10 minute lecture on how AntiSamy .Net is the latest and greatest in XSS protection (we also still use XP, so maybe there is a connection). I tried to let him know AntiSamy .Net hasn't been in production for years, but he told me that he is a manager and management is always right.
Technicaly, he pays my bills, so I'll give him what ever service he wants; however, the documentation and links for installing the .Net version is about as abundant as Irish potatoes in 1850.
Would someone be kind enough to point me in the right direction?
[COMTEC 2012 Register Now]<http://www.touchnet.com/comtec/>
This electronic mail transmission, including any accompanying attachments, is intended solely for its authorized recipient(s). If you are not the intended recipient, please be aware that any disclosure, copying, distribution or use of the contents of this message is strictly prohibited. If you received this transmission in error, immediately contact the sender and delete the contents and attachments of this message.
Note to recipient: This is an unsecured email service which is not intended for sending confidential or highly sensitive information. Confidential or highly sensitive information includes, but is not limited to, payment card information, social security numbers, and account numbers.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Owasp-antisamy