summaryrefslogtreecommitdiff
path: root/old/published/Webmonkey/Monkey_Bites/2007/08.13.07/Fri/skype.txt
diff options
context:
space:
mode:
authorluxagraf <sng@luxagraf.net>2020-04-28 10:24:02 -0400
committerluxagraf <sng@luxagraf.net>2020-04-28 10:24:02 -0400
commitf343ef4d92352f9fc442aeb9c8b1abee27d74c62 (patch)
tree4df5c497e7caeab1f8932df98ad3d00fef228a3e /old/published/Webmonkey/Monkey_Bites/2007/08.13.07/Fri/skype.txt
parenta222e73b9d352f7dd53027832d04dc531cdf217e (diff)
cleaned up wired import
Diffstat (limited to 'old/published/Webmonkey/Monkey_Bites/2007/08.13.07/Fri/skype.txt')
-rw-r--r--old/published/Webmonkey/Monkey_Bites/2007/08.13.07/Fri/skype.txt20
1 files changed, 0 insertions, 20 deletions
diff --git a/old/published/Webmonkey/Monkey_Bites/2007/08.13.07/Fri/skype.txt b/old/published/Webmonkey/Monkey_Bites/2007/08.13.07/Fri/skype.txt
deleted file mode 100644
index 13fbf96..0000000
--- a/old/published/Webmonkey/Monkey_Bites/2007/08.13.07/Fri/skype.txt
+++ /dev/null
@@ -1,20 +0,0 @@
-Yesterday, while testing the new Skype of Mac beta, we noticed that the service was experiencing some server problems and the Skype posted a note admitting as much and claiming the issue would be resolved in twenty-four hours.
-
-While Skype isn't completely back up for all users, it appears that a significant portion of the network is back up and running, though what went wrong is still a little unclear.
-
-Yesterday, George Ou at ZDNet posted a [message][4] from Valery Marchuk of SecurityLab.ru which claimed that a code exploit published by an anonymous user could have been the culprit in the Skype outage, a charge Skype denies.
-
-There's a new note up on the Skype "Heartbeat" page [which reads][2]:
-
->Apologies for the delay, but we can now update you on the Skype sign-on issue. As we continue to work hard at resolving the problem, we wanted to dispel some of the concerns that you may have. The Skype system has not crashed or been victim of a cyber attack. We love our customers too much to let that happen. This problem occurred because of a deficiency in an algorithm within Skype networking software. This controls the interaction between the user’s own Skype client and the rest of the Skype network.
-
-Although Skype has [not responded][3] to most media inquires, Skype representatives [tell the New York Times][1]: "This problem occurred because of a deficiency in an algorithm within Skype networking software. This controls the interaction between the user's own Skype client and the rest of the Skype network."
-
-They also went on to say that the service may not be fully restored for a little while. "There is a chance this could go on beyond tomorrow, but it’s our hope that it’s going to be resolved," said Kurt Sauer, Skype’s chief security officer.
-
-Apparently Skype knows what the problem is, but can't seem to find a way to fix it. So far the outage has affected an estimated 220 million users.
-
-[1]: http://www.nytimes.com/2007/08/17/business/17ebay.html?ex=1345003200&en=cccaa6da8a8347fb&ei=5090&partner=rssuserland&emc=rss
-[2]: http://heartbeat.skype.com/2007/08/the_latest_on_the_skype_signon.html
-[3]: http://blog.wired.com/business/2007/08/skype-wont-comm.html
-[4]: http://blogs.zdnet.com/Ou/?p=683 \ No newline at end of file