|Product Name||Double Cross Blind|
|Category||Book / Magazine / Publication|
|Amazon.com||Buy on Amazon ~ 0739319558|
|Long Description||December 1, 1941 It is seven days before the Japanese attack Pearl Harbor. Days that are numbered for Sondegger, a Nazi spy captured in London while on a mission to take down the Twenty Committee, a German network of spies the British have turned. For American Tom Wall, the days have run together as he awakens to find himself locked in a British military asylum. Wounded and shell-shocked, all he knows is that his brother, Earl, betrayed his unit in Crete, causing one of the bloodiest massacres of the war. MI5 releases Tom by way of a bargain. Pretend to be Earl and convince Sondegger to reveal how and where he has arranged to transmit his intelligence to Germany. Fail, and spend the rest of the war in jail. Succeed, and Tom, though still considered a danger to himself, will be allowed to leave the hospital to find Earl—who may well be a Nazi informant. But Sondegger proves himself to be a formidable opponent. Even as he surrendered himself to the British, he knew the Japanese fleet had sailed for Pearl Harbor. The question is: Who will gain more if the Allies prevent the attack? Sondegger, MI5, the OSS, Tom, and Earl’s wife, Harriet, all have different answers. Unable to trust anyone, Tom attempts to save the Twenty Committee and stop the attack on Pearl Harbor as the clock counts down. In his electrifying debut, Joel Ross combines political insights with the high stakes and fast pace of classic espionage fiction, and he delivers what others have not in more than a decade—a Nazi spy novel that you cannot put down.|
|Search Google||by EAN or by Title|
Article of interest
We are not hosted at GoDaddy, but we are registered there and have our DSN settings stored with them. So when Anonymous attacked GoDaddy, we were impacted too.
It is very sad that hackers don't think about all of the people that will be impacted by their actions. Even though we were not attacked directly, we were impacted and most of our users were also impacted.
Our site was up and running the entire time and because many DNS servers cache the address to our site, we had a steady flow of traffic during the attack. But the number of visiters to the site was clearly lower than normal. We had a significant drop in visitors and even after things were fixed by GoDaddy things weren't quite normal again until quite late in the evening.
If you or your applications were impacted by this attack we are deeply sorry but there was nothing that we could do to prevent or recover from this. Just like you, all we could do is wait for GoDaddy to deal with the situation.
Here are some news links you can read relating to the attack:
Update 9/13/2012 - It appears that this may not have been an attack after all. GoDaddy is saying that this was not an attack but a configuration error that cascaded through their routers taking their services off line for about six hours. Be it an attack or an accidental configuration issue makes no real difference to the end users that couldn't gain access to the web sites hosted on or registered with GoDaddy.
Although this was all very annoying, no personal information seems to have been accessed such as passwords, credit card numbers, addresses, phone numbers or alike. Personally, being a technical person, I feel GoDaddy handled this situation quite well. I am not happy that it happened or that our users were unable to get to the site. But the tech team at GoDaddy did a very good job at correcting the problems.