Anatomy of a web hack One of my websites recently got hacked (through FTP - provider says its password related, but I'm not convinced). The miscreant put over 5000 HTML pages in one of my directories, each of which is infected with a piece of obfuscated javascript. I've tidied it up for readability :-


What this does is call another script from another domain (dnsmanagersite.info). This script, in turn, forces a redirect to a porn site, which tries to force you to download what it claims is an update for Adobe Flash. I have no doubt at all that it is a virus/trojan/keylogger/backdoor or other such piece of crap.  ¶ 11:50 AM 0 Comments Links to this post

  The trouble with AJAX frameworks... As my brother would say, I've been busier than a one-legged Riverdancer just lately....

I'm working for two clients simultaneously - a mix of Classic ASP and ASP.Net by day and PHP5 by night. In both cases, I'm making use of AJAX Frameworks and herein lies the problem. Conceptually, using a framework rather than dong everything yourself "from scratch" is a good thing, since it should save re-inventing the wheel.

However, I'm finding in both cases (Microsoft ASP.Net Ajax for one, QCodo for the other) that things are either incomplete, inadequately documented, or just plain broken. I'm increasingly finding myself spending more time fixing little rendering issues (or things that don't render at all) and less time dealing with the core functionality of the application.

Its frustrating, to say the least.
  ¶ 9:01 PM 1 Comments Links to this post