skypeopensource
Joined 15 years ago
Karma
139
Submissions
65
Member since
Jun 2
Recent submissions
Comment · 10 years ago
Skype Network is proprietary and closed, but used by around 500 mln users (or more) per month.
Comment · 10 years ago
Thank you for very clear and detail answer.
Comment · 10 years ago
Comment · 10 years ago
> I remember seeing an earlier incarnation of this around five years ago
Yes, its still up here: https://skype-open-source2.blogspot.com/
Comment · 10 years ago
> Does anyone have a link to a write up on this?
Here was a little insight:
https://nakedsecurity.sophos.com/2011/06/03/skype-protocol-c...
Comment · 10 years ago
Reversing are explicitly allowed in EU government as other based human laws.
I mean, EU have a much more great priority then Skype TOS.
If someone will add to Skype TOS "and please dont breath or dont go to toilets during use of our application". It will have zero effects in legal meaning. Because it break upfront law and United Nations based rights and etc.
tldr;
They just try to fear you with "dont do this" thing.
Comment · 10 years ago
Yes :-)
Comment · 10 years ago
Protocol from Skype Desktop version.
Comment · 10 years ago
And break all the mess of 10 mln users online at once, and around 500 mln at month. With big zoo of various versions. Even if they do so, reversing new tweaks not take too long.
Also, you have good working proto. Do changes to it daily... For that reason? Just because someone write compatible client (very buggy, by the way, and less of features)? I dont think so.
Comment · 10 years ago
Working version of first Skype Network compatible client (Epycs) which creation was based on this protocol dumps will be released 1 september 2016.
Comment · 10 years ago
Hello guys,
this is some thougts and result of my investigation into skype protocol and how it is worked.
First of all, what we need to reconstruct network protocol?
We need plain text data which transfered from host A to host B, right? Right. So, there it is. There is a text files with plain text data which sended from one skype client to another skype client. Yes, it have much crypto on lower levels. For now, just dont think about it. It was researched one time and after we just encapsulate it in function or class and dont care about it. Text files of skype send message sequence:
http://dev.epycslib.ru/dumps/parse_proto.zip
Okay, we got plain text data transfered. What we need next? We need understand, that all this data means. Where is destination username, where is time and where is message. And how protocol care it all for working good. How to do this? Best way, its rewrite it on paper in your own blocks and visual representation to understand internal structure of protocol. Make visual blocks and etc. Like in UML. So, there it is. My scans of hand written paper with skype protocol send message sequences:
http://dev.epycslib.ru/dumps/skypeproto.zip
More info at:
http://skype-open-source2.blogspot.ru/2016/06/skype-protocol...