Hacker News new | ask | show | jobs
by itsprofitbaron 4908 days ago
Regarding your Security point, the fundamental problem with HTML5 and the way online banks use their security is that with HTML5 ultimately the user has control over the code which is running on their machine. Browsers come with decent debugging tools making it easier to abuse (and there are even better ones as plugins).

Using the browsers debugger (or your one of choice) you can simply go to a website running on HTML5 and insert a few breakpoints and watch what happens. All someone would have to do is edit the variable(s) which hold the data to anything they'd desire.

You can argue there are limits to these potential exploitations but some of the tools are as complicated as the complier itself - and when companies are trying to push out a feature as quickly as possible, security issues are often overlooked. For example have a look (if you haven't already) at http://plaintextoffenders.com/ which shows websites which store passwords in plain text. Sure my example relates to a different issue but if websites are prepared to store passwords in plain text then inevitably, they will overlook other potential security issues.

When money is involved, any minor potential exploitation is taken advantage to the fullest extent. Hence I still believe HTML5 apps shouldn't be trusted with any serious data collection.