skypeopensource

Skype Network is proprietary and closed, but used by around 500 mln users (or more) per month.

Thank you for very clear and detail answer.

> I remember seeing an earlier incarnation of this around five years ago

Yes, its still up here: https://skype-open-source2.blogspot.com/

> 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...

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.

Yes :-)

Protocol from Skype Desktop version.

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.

Working version of first Skype Network compatible client (Epycs) which creation was based on this protocol dumps will be released 1 september 2016.

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...

+15 USD

+15 USD

So, for now, only four people will be on about page in first ever skype network compatible client. Lucky guys!

At this moment i have:

Paypal:

50 USD

10 USD

4 GBP

10 USD

Nice work, before all. Really. My respects.

Web use new proto. Which is not our aim at all.

My contact info in social networks, btw. And email.

skypeopensource@gmail.com http://vk.com/efim.bushmanov https://www.facebook.com/efim.bushmanov

I post links on tor... But ints not help much. Against be DMCA'ed.

"and use what you learned to make a profit"

I am not. Problem was in different case. I should not post patched skype binaries, needed for reverse engineering. And its okay, what i will be shotdown for use it.

Yes, your are right. Its kind of big risk. But we have some situation in past. It is ICQ vs Miranda case. And all still alive and usable.

EU law explicitly allow reversing for compatibility issues. Which exactly what i am doing.

:))

Chicken or pork are also appreciated!

I dont sure, if will be ok to host some kind of this project.

Because kind of this project.

Yeah. We can still talking about paypal policy, instead of topic.

DMCA is not main problem, for now.

"Why not just put this on indiegogo or kickstarter"

I just dont sure, which is will ok with this kind of projects...

Yes...

You are clean right. But for now, we have worked:

1) login (get auth credentials)

2) get contact list

3) find vcard of the given user

4) do relay connect for it

5) send or recv message from it

Its buggy for some reasons, but its worked.

However, yes, its not released an its not public, to not ruin my work until release date.

"decompiled code" its hard to proof for DMCA. No, situation was simple, i upload hacked skype binaries in repo for easy distribution. And this is no-no clear case for DMCA takedown. So, it happens.