<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>AntiXSS Library V3.0 - Test Harness</title><link>http://blogs.msdn.com/cisg/archive/2009/01/19/antixss-library-v3-0-test-harness.aspx</link><description>Hi, Anil Chintala here&amp;#8230; In this post I wanted to talk about the new Test Harness application which was released as part of the AntiXSS V3.0 Beta and is available as a free download on MSDN with source code available for download on CodePlex . Test</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: AntiXSS Library V3.0 - Test Harness</title><link>http://blogs.msdn.com/cisg/archive/2009/01/19/antixss-library-v3-0-test-harness.aspx#9340534</link><pubDate>Mon, 19 Jan 2009 21:55:41 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9340534</guid><dc:creator>jeff.williams@owasp.org</dc:creator><description>&lt;p&gt;I meant to post on this earlier. Performing HTML entity encoding on all of RSnake's attack vectors is just plain silly. You might as well run it on Moby Dick. A better approach would be to actually go through the vectors and apply exactly the right encoding for each context. BTW, does AntiXSS pass these - &lt;a rel="nofollow" target="_new" href="http://code.google.com/p/owasp-esapi-java/source/browse/trunk/src/test/java/org/owasp/esapi/reference/EncoderTest.java?"&gt;http://code.google.com/p/owasp-esapi-java/source/browse/trunk/src/test/java/org/owasp/esapi/reference/EncoderTest.java?&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>re: AntiXSS Library V3.0 - Test Harness</title><link>http://blogs.msdn.com/cisg/archive/2009/01/19/antixss-library-v3-0-test-harness.aspx#9341879</link><pubDate>Tue, 20 Jan 2009 06:19:27 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9341879</guid><dc:creator>Jesper Lind</dc:creator><description>&lt;p&gt;Can you please let us know how to use the ddl:s on a host with medium trust? We have coded stuff that works great on our local machines, but we have not managed to run this in partial trust. &lt;/p&gt;
&lt;p&gt;Yes we have tried to compile it our self with AllowPartiallyTrustedCallers, but it does not work. &lt;/p&gt;
&lt;p&gt;Also posted the question here: &lt;a rel="nofollow" target="_new" href="http://www.codeplex.com/AntiXSS/Thread/View.aspx?ThreadId=44517"&gt;http://www.codeplex.com/AntiXSS/Thread/View.aspx?ThreadId=44517&lt;/a&gt;&lt;/p&gt;</description></item><item><title>AntiXSS Library V3.0 - How to run in partial trust?</title><link>http://blogs.msdn.com/cisg/archive/2009/01/19/antixss-library-v3-0-test-harness.aspx#9386604</link><pubDate>Sat, 31 Jan 2009 20:23:33 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9386604</guid><dc:creator>Jesper Lind</dc:creator><description>&lt;p&gt;I really would like to use the AntiXSS but have not yet been able to run it on medium trust. I found some people who also wonder how to do it and nobody have a solution.&lt;/p&gt;
&lt;p&gt;I also posted the question on CodePlex some time ago. Any help with this would be great.&lt;/p&gt;
&lt;p&gt;&lt;a rel="nofollow" target="_new" href="http://www.codeplex.com/AntiXSS/Thread/View.aspx?ThreadId=44517"&gt;http://www.codeplex.com/AntiXSS/Thread/View.aspx?ThreadId=44517&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Information Security &amp; Performance</title><link>http://blogs.msdn.com/cisg/archive/2009/01/19/antixss-library-v3-0-test-harness.aspx#9484484</link><pubDate>Tue, 17 Mar 2009 22:12:44 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9484484</guid><dc:creator>Information Security</dc:creator><description>&lt;p&gt;Our mission in Information Security is to enable secure &amp;amp;amp; reliable business . In going about our&lt;/p&gt;
</description></item></channel></rss>