jf wrote:This seems to be linked to the Hare Computer Virus. In this article, they say: The virus was set to read the system date of the computer and activate on August 22 and September 22 http://en.wikipedia.org/wiki/Hare_%28computer_virus%29
I tried this: changing my computer clock to 22-Aug-1996 2:57 and reloading the site (websites can actually read the user browser version, screen resolution, etc... and probably user computer time). Nothing happened.
Could someone double-check this?
People claim it worked... I find it flimsy so far but the fact that the code shows the position of the code etc. means that there is something there to find.
javascript update: finished skirting through the code, don't see anything else that looks like a clue. There is a reference to a 5000 try limit on the password but it doesn't actually check it clientside.
where <yourpasswordhere> is your attempt. You then get two fields back, 'error' and 'url'. If 'error' returns false, you get forwarded to the supplied url. So there's definitely a password to crack here.
jf wrote:This seems to be linked to the Hare Computer Virus. In this article, they say: The virus was set to read the system date of the computer and activate on August 22 and September 22 http://en.wikipedia.org/wiki/Hare_%28computer_virus%29
I tried this: changing my computer clock to 22-Aug-1996 2:57 and reloading the site (websites can actually read the user browser version, screen resolution, etc... and probably user computer time). Nothing happened.
Could someone double-check this?
People claim it worked... I find it flimsy so far but the fact that the code shows the position of the code etc. means that there is something there to find.
jf wrote:This seems to be linked to the Hare Computer Virus. In this article, they say: The virus was set to read the system date of the computer and activate on August 22 and September 22 http://en.wikipedia.org/wiki/Hare_%28computer_virus%29
I tried this: changing my computer clock to 22-Aug-1996 2:57 and reloading the site (websites can actually read the user browser version, screen resolution, etc... and probably user computer time). Nothing happened.
