Continued from page 1
I overcame this obstacle when I found the Cisco XoT (x.25 over TCP) specification (Internet standard RFC1613). Later, my experience with the protocols for the x25 networks, which are very closed and proprietary, helped me a lot in my research on the Skype protocol.
So I like the challenge of research into proprietary objects precisely because they are complex, closed things. Many people see them as useless and a complete waste of time, but they are, in a very real sense, the mechanisms of our daily online lives.
But I also like to work on web technologies. I code in Python and Perl, sometimes with ajax/jquery.
Why did you decide to create this open source version of Skype? What was your motivation?
First of all, this was a very exciting reverse engineering challenge. Skype presents a lot of questions regarding security. I was simply curious to know what was inside.
I like Skype. It is a good product. Most importantly, it is well-tested and fine-tuned. Open source products cannot match that level of polish.
I don’t intend and I have no plans to compete with Skype in any way. Let this good product remain as it is. I just wanted to create a product compatible for all Linux users who are waiting impatiently for it. For example, we could make a jabber/XMPP/gmail gateway to Skype and a “real” pidgin plugin for it. An open source version, in addition, will be useful to everyone.
When did you start this work? How long did it take you? Did you do it alone?
I started to take an interest in Skype in February 2008, when I received the de-obfuscated skype14.exe binary.
I didn’t work on this project continually, just from time to time. The most active phase was between 2008 and 2010, with some interruptions.
It looked like a pipe dream in the beginning, but then it became more exciting, and I took up a blackbox approach to the project. The security layers came off, one after the other. But the job remains unfinished!
The de-obfuscated skype 14 binary I had made it much easier to me than to other researchers, although a lot of research on this has been available since 2006. The most interesting studies have come from the Sean O’Neil’s VEST Corporation and the guys at EADS.net – particularly ‘Vanilla Skype,’ and then ‘Silver Needle’ and other presentations.
Continued on page 3
Explore the future of work with the Silicon In Focus Podcast. Discover how AI is…
Executive hits out at the DoJ's “staggering proposal” to force Google to sell off its…
US prosecutors confirm earlier reports, demand Google sells off Chrome web browser and end default…
Following Australia? Technology secretary Peter Kyle says possible ban on social media for under-16s in…
Restructuring expert appointed to oversea Northvolt's main facility in northern Sweden, amid financial worries
British competition watchdog decides Alphabet's partnership with AI startup Anthropic does not qualify for investigation
View Comments
I think the proprietary nature of Skype is its biggest downfall. Dominant proprietary monoliths have little concern about the user experience and represent a huge risk to anyone who would tie their future to such a technology.
Just one example of how Microskype will benefit from its code being "outed" is in regaining adoption by those of us who have been alienated by the flashing advertising in the Skype client: there will be an alternative.
It's also a small step towards reassuring businesses who don't want to tie their investment to Microskype, which may change to become uneconomic in the future, that they may be able to make a quick switch to another service based on the same technology.
Nice article about russian via skype, I took few lessons with a native speaker through http://preply.com/en/russian-by-skype and I am pretty satisfied with the quality presented, but I would like to try another option