Blogs On Blogspot Have Malware & Trojans But Wordpress Blogs Safe - Says Google
Thursday, May 29, 2008

Google's new anti malware advisory services tells you whether a site is safe to browse or does it contain any Malware, Trojans or malicious scripts that may pose security risk.
The Google's anti malware advisory service reporting 208 blogs hosted on blogspot.com to be functioning as intermediaries for distributing malware to visitors of this site. Where as blogs hosted on wordpress.com are very safe and not even a single blog is reported as threat.
Here are the few points from the report on blogs hosted by blogspot.com
1. 227 suspicious activities are recorded over the past 90 days
2. 5880 torjans, 844 scripting exploits and 262 adwares are identified
3. Successful infection resulted in an average of 4 new processes on the target machine
Read the full advisory report of blogger.com and wordpress.com for more details.
You can view Google Anti Malware Advisory diagnostic report of a any web site by appending the web site name to the url "http://www.google.com/safebrowsing/diagnostic?site=". For example using the url
http://www.google.com/safebrowsing/diagnostic?site=tricks2trick.blogspot.com
you can view report of Tricks 2 Trick
The reports gives answers to the following questions
1. What is the current listing status?
2. What happened when Google visited this site?
3. Has this site acted as an intermediary resulting in further distribution of malware?
4. Has this site hosted malware?
End of Internet is near
Saturday, March 15, 2008
Programs will fail, of course. Since they will see times not as being in 2038 but rather in 1901, erroneous calculations and decisions will occur. (It's true, check Wikipedia!) Demo Example showing how the date would reset (at 03:14:08 UTC on 19 January 2038). We've actually seen fallout from the 2038 bug already, back in May of 2006 when the AOLserver web server software crashed. The software was designed so that database requests would "never" time out. Instead of assigning a "0" to the timeout, the software specified a timeout date one billion seconds in the future. One billion seconds (just over 31 years 251 days and 12 hours) after 21:27:28 on 12 May 2006 is beyond the 2038 cutoff date. The system calculated a timeout date that was actually in the past, got confused, and crashed. The bug even affected the Mars Rover! Check out the archived outputs from test scripts here: (Source: the 2038 FAQ) Before mass hysteria sets in, let's all remember that we have years, decades even, to deal with this latest programming glitch. And as for the internet? Well, I'm pretty sure that self-improving Artificial Intelligences will be running the world by then, so we probably don't need to worry too much about this.
Have you heard the latest doomsday scenario? In thirty years, the internet will stop working! Apparently, a bug similar to the millennium bug will affect Unix-based systems, like those that run the tubes, in the year 2038. The bug, being dubbed the "2038 bug," arises because Unix-based systems store the time as a signed 32-bit integer, in seconds, from midnight on January 1 1970. And the latest time that can be represented in that format, by the Posix standard, is 3:14 AM on January 19, 2038. After that, times will wrap around and be represented as a negative number.And then what happens?

Want More Proof?
What's Affected?
By 2038, it's likely that many of the susceptible machines will have been decommissioned before the critical date occurs. However, legacy systems and embedded systems could still be affected. These may include process control computers, space probe computers, embedded systems in traffic light controllers, navigation systems, routers, gas pumps, etc. It may not be possible to upgrade many of these systems, so they will need to be replaced.
I'm a Programmer - What Can I Do?
The End?
Labels: Bugs, Technology
