<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://weblogs.asp.net/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>Daveloper's Blog - All Comments</title><link>http://weblogs.asp.net/daveloper/default.aspx</link><description>Daveloper.Brain.ToString();</description><dc:language>en</dc:language><generator>CommunityServer 2007 SP1 (Debug Build: 20510.895)</generator><item><title>re: Silverlight Security Concepts</title><link>http://weblogs.asp.net/daveloper/archive/2008/04/01/silverlight-security-concepts.aspx#7133685</link><pubDate>Wed, 24 Jun 2009 20:09:11 GMT</pubDate><guid isPermaLink="false">c06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:7133685</guid><dc:creator>Jim</dc:creator><description>&lt;p&gt;What keeps an attacker from simply modifying your client-side code? For example why not find where the password is checked and modify the code to continue whether the password is correct or not?&lt;/p&gt;
&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=7133685" width="1" height="1"&gt;</description></item><item><title>re: Silverlight Security Concepts</title><link>http://weblogs.asp.net/daveloper/archive/2008/04/01/silverlight-security-concepts.aspx#7097492</link><pubDate>Mon, 25 May 2009 17:06:28 GMT</pubDate><guid isPermaLink="false">c06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:7097492</guid><dc:creator>laguy88</dc:creator><description>&lt;p&gt;Hi Dave,&lt;/p&gt;
&lt;p&gt;A year since this post ( May 25, 2009 ) and Silverlight 2 is out with SL 3 coming soon.&lt;/p&gt;
&lt;p&gt;Any more comments on Security of &amp;quot;source code&amp;quot; or &lt;/p&gt;
&lt;p&gt;security authentication using WCF ?&lt;/p&gt;
&lt;p&gt;Happy Memorial Day weekend, LA Guy&lt;/p&gt;
&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=7097492" width="1" height="1"&gt;</description></item></channel></rss>