Ajax Security Tools
IdaAshley points out the latest from IBM developerWorks' Web development section, which talks about shoring up potential weaknesses in Ajax applications. It follows another recent guide for improving Ajax performance.
"In this article, you'll learn about Ajax security tools, which you'll be using to scan for SQL injection and cross-site scripting vulnerabilities; to set a master password; and to restore the state of all windows after crashes. You'll take a look at tools and utilities that ensure that linked Web sites in applications are not on the blocked lists and which prevent hackers from altering browser functionality, defacing Web applications, and achieving malicious results. You'll find these utilities divided into three types within the article: hardening tools, Firefox tools, and Firefox add-ons."
This is a great article, because it's given me exactly what I needed. Thanks to Ajax and IBM, I've already got a hardening tool right here in my hand.
You lie!
Ajax was second only to Achilles during the Trojan War! And Achilles--oh wait. Perhaps he does have a weakness. But considering that he didn't die while Achilles did, I think we can safely say that when you associate security and Ajax in one sentence you had better be talking about security against Ajax. Ajax is strong, not weak! It is the application programmers that are weak. Let's see them take on the Trojans before they complain about Ajax's weaknesses.
It's a pity that the web is becoming an application development platform, because it really sucks as an API. Unfortunately all other contenders are either too much like the web (XUL) or proprietary (Silverlight, Flex). Browser security is a bitch with just web pages. Wait until people expect cross-site integration from their web applications...
What can you do? People want their cake, and to eat it too.
Incidentally, don't make your cakes with Ajax. It will kill you.
Maybe offtopic, but does anyone know what the new hotness is, java/jsp/j2ee wise, wrt ajax frameworks? I've forked around with echo2 but I'm not totally sold.
I can google all I want, but I'd love some opinions.
You're right.
The main burden of blame should fall on the 'frontend HTML guys' who are often folks who got good at Dreamweaver (maybe they're "hard-core" and use notepad!! omg!!111lol) and ColdFusion, and now fancy themselves "web 2.0" professionals.
So many of the development "tools" (code for "wizard") out there do *just enough* to let these amateurs function, but barely.
These people should've stayed out of the business, as their buggy and gaudy sites will attest.
Not really sure what this has to do with AJAX security, thanks IBM!
But wow, that was fucking terrible.
Isn't that an oxymoron?
Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.