<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.4" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Some simple XSS Attacks by Example</title>
	<link>http://ericfarraro.com/?p=8</link>
	<description>Software development in the daily life of Eric Farraro</description>
	<pubDate>Sun, 05 Sep 2010 17:04:40 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.4</generator>

	<item>
		<title>by: Matt</title>
		<link>http://ericfarraro.com/?p=8#comment-2106</link>
		<pubDate>Tue, 12 Dec 2006 23:19:38 +0000</pubDate>
		<guid>http://ericfarraro.com/?p=8#comment-2106</guid>
					<description>Not sure inserting javascript (client side code) into the html is the best example of the security issues on this but I guess the point is made.</description>
		<content:encoded><![CDATA[<p>Not sure inserting javascript (client side code) into the html is the best example of the security issues on this but I guess the point is made.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: GraemeL</title>
		<link>http://ericfarraro.com/?p=8#comment-96</link>
		<pubDate>Thu, 28 Sep 2006 11:16:32 +0000</pubDate>
		<guid>http://ericfarraro.com/?p=8#comment-96</guid>
					<description>As Vijay says, you must perform all validation and sanitization on the server side, even if you (think) you've already done it on the client.

Every programmer should know the three golden rules for programming on the web:

Rule 1: Never trust the client.
Rule 2: Never trust the client.
Rule 3: Never trust the client.</description>
		<content:encoded><![CDATA[<p>As Vijay says, you must perform all validation and sanitization on the server side, even if you (think) you&#8217;ve already done it on the client.</p>
<p>Every programmer should know the three golden rules for programming on the web:</p>
<p>Rule 1: Never trust the client.<br />
Rule 2: Never trust the client.<br />
Rule 3: Never trust the client.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Computer Science Canada Blog &#187; XSS and SQL Injections from user input</title>
		<link>http://ericfarraro.com/?p=8#comment-94</link>
		<pubDate>Thu, 28 Sep 2006 03:17:16 +0000</pubDate>
		<guid>http://ericfarraro.com/?p=8#comment-94</guid>
					<description>[...] Having been stressing online forms of my fellow developers at work, and reading Eric Farraro's posts on Cross Site Scripting and his recent Google exploit, I figured just how important user input validation is, and the need to emphasise that. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Having been stressing online forms of my fellow developers at work, and reading Eric Farraro&#8217;s posts on Cross Site Scripting and his recent Google exploit, I figured just how important user input validation is, and the need to emphasise that. [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Vijay</title>
		<link>http://ericfarraro.com/?p=8#comment-87</link>
		<pubDate>Mon, 25 Sep 2006 15:34:32 +0000</pubDate>
		<guid>http://ericfarraro.com/?p=8#comment-87</guid>
					<description>Basically all client side validations are useless, we can override them with ease. Either by modifying the page content using javascript, or by writing a program that does a direct POST to the form processor. All error processing needs to be shifted to server side, if you really wan't a 'secure' site. Client side validation is only to improve user experience. That is where AJAX can come to help, doing realtime validation without page reloads, yet doing it on the server side. Also we should check for %XX characters in the fields. If '' is blocked, some hackers may get around using %3C or %3E.</description>
		<content:encoded><![CDATA[<p>Basically all client side validations are useless, we can override them with ease. Either by modifying the page content using javascript, or by writing a program that does a direct POST to the form processor. All error processing needs to be shifted to server side, if you really wan&#8217;t a &#8217;secure&#8217; site. Client side validation is only to improve user experience. That is where AJAX can come to help, doing realtime validation without page reloads, yet doing it on the server side. Also we should check for %XX characters in the fields. If &#8216;&#8217; is blocked, some hackers may get around using %3C or %3E.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Tony</title>
		<link>http://ericfarraro.com/?p=8#comment-86</link>
		<pubDate>Mon, 25 Sep 2006 13:09:57 +0000</pubDate>
		<guid>http://ericfarraro.com/?p=8#comment-86</guid>
					<description>the ideas mentioned here are very similar to to SQL injection techniques, just substitute JavaScript for SQL. The bottom line is that all user input needs to be sanitized and checked.

So - any suggestions for a 'secure' site that doesn't severely limit use experience? I used to have a LiveJournal blog until I got fed up with them turning everything off, and just installed my own WordPress.

(Btw, Opera browser also allows one to edit page's contents and reload it from cache, just not as graphical as Firefox's plugin)</description>
		<content:encoded><![CDATA[<p>the ideas mentioned here are very similar to to SQL injection techniques, just substitute JavaScript for SQL. The bottom line is that all user input needs to be sanitized and checked.</p>
<p>So - any suggestions for a &#8217;secure&#8217; site that doesn&#8217;t severely limit use experience? I used to have a LiveJournal blog until I got fed up with them turning everything off, and just installed my own WordPress.</p>
<p>(Btw, Opera browser also allows one to edit page&#8217;s contents and reload it from cache, just not as graphical as Firefox&#8217;s plugin)
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
