Skype-open-source2: Call to donate
skype-open-source2.blogspot.com
skype-open-source2.blogspot.com
I am Efim Bushmanov skype reverse engineer with first publish of original work on reversing skype client at June of 2011. And i almost done work on create open source version of "Skype Network Compatible" client.
Some info about me: https://nakedsecurity.sophos.com/2011/06/03/skype-protocol-c... https://news.ycombinator.com/item?id=2611299 http://github.com/skypeopensource/
And now I need some help from community. Thats why i do donate call.
Feel free to ask question about current state and any tech question. But, i will be prefer, if possible, not disclosure much, for reason ms-skype dont ruin my work too early by do some changing protocol again. But you feel free to ask some technical details or general question at all of how skype work.
You can read more at: http://skype-open-source2.blogspot.ru/2016/03/call-to-donate...
I don't understand the point of the semi-secrecy. There's almost certainly hundreds of MS employees on this site which means you've lost that advantage already, and anyway you're going to have the same problem after you release the software.
Are there public code hosting (gitlab?) in other countries, where the dmca does not apply? maybe something in Europe, where reverse engineering might be less strict?
I just dont sure, which is will ok with this kind of projects...
I would suggest asking.
Edit: Unfortunately, I also don't really do bitcoin and have never heard of the other two options.
I suppose you could always try offering him some chickens or something?
Chicken or pork are also appreciated!
It might help to have multiple popular avenues for donation.
The only thing worse than them taking my money was talking to the ignorant assholes on the phone about it.
They did eventually return it, more than a year later, with no explanation. Just suddenly my account balance increased. No interest payments for the time it was stolen though.
They claimed suspicious activity, when it was in fact a client trying to pay me. Go figure.
I know it's petty but I'm telling you this for your own sake.
Besides, this reverse engineering work should be simpler now that Skype was bought by Microsoft. For example, Microsoft no longer encrypts/destroys the executable's import table. And it seems they dumped the anti-debugger code too.
Let's also not forget Microsoft is pushing out new variants that should lend themselves to reverse engineering (e.g. web/plugin-free [0] and Universal Windows Platform [1] apps).
---
[0] https://support.skype.com/en/faq/FA12316/what-is-the-skype-w...
[1] http://blogs.skype.com/2016/03/24/skype-universal-windows-pl...
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.
It has less documentation, but still is plaintext-over-TLS, unlike the legacy (and, arguably, less reliable as well) supernode protocol the poster has been reverse engineering for the past years.
The problem is, as you reverse-engineer Skype and release source code that is meant to be liberally licensed, it still could be that the code would be practically unusable, due to possible legal issues.
IANAL, but from my understanding of the law, this is even a gray area in Russia (local RE laws restrict on what you can do with the obtained knowledge, and the law's wording feels pretty vague to me), and even if legal here, an US or EU court may have a different idea.
Maybe that's not true and I'm just over-cautious, but... well... there's clean-room reverse engineering (where one engineer analyzes the product and writes comprehensive documentation suite and another, completely unrelated person, reads the documentation and writes actual code) for a reason.
Also, the ToS for Skype may forbid the use of inofficial clients, and users using these might be locked out of the service if Skype finds out and cares.
However, one big issue I forsee is issues with Skype changing their API/protocol and completely breaking the open source alternative. Updating would require a constant stream of development work which, if past projects of this type are anything to judge by, may be difficult or impossible to supply.
skypeopensource@gmail.com http://vk.com/efim.bushmanov https://www.facebook.com/efim.bushmanov
Well one of the repo's
And I move all my source files (except forbidden to publish skype patched binaries) to repo named Epycs (skype word in reversed letters).
Also, why not just work on a free software replacement for Skype? That way people could use your code without being threatened by patent suits and other legal arsenal wielded by Microsoft.
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.
"...An objective of this exception is to make it possible to connect all components of a computer system, including those of different manufacturers, so that they can work together."
And the US: Sec. 103(f) of the DMCA (17 U.S.C. § 1201 (f)) says that a person who is in legal possession of a program, is permitted to reverse-engineer and circumvent its protection if this is necessary in order to achieve "interoperability" - a term broadly covering other devices and programs being able to interact with it, make use of it, and to use and transfer data to and from it, in useful ways. A limited exemption exists that allows the knowledge thus gained to be shared and used for interoperability purposes.
Paypal:
50 USD
10 USD
4 GBP
10 USD