Hello, wiki.epycs.ru available again.
I think wiretapping is one of the big reasons for the rearchitecture. Skype officially claimed they could not comply with wiretapping requests because of the P2P network as late as 2008 (http://news.cnet.com/8301-13578_3-9963028-38.html), and Microsoft was already working on wiretapping VoIP in 2009 (http://blog.tmcnet.com/blog/tom-keating/microsoft-patents-voip-and-skype-wiretapping.asp).via Hacker News
Relay nodes take care of those if you can't communicate directly with the other end. There is a mutual exclusivity in that a node can't be a relay and a supernode at the same time.Can he prove it? No. But, I can. This code, which I wrote in past, will allow for your traffic to flow via supernode(and also relay node): skyrel.c skypush.c
Skype user IP-address disclosure
1. Download this patched version of Skype 5.5:
2. Turn on debug-log file creation via adding a few registry keys.
3. Make "add a Skype contact" action, but do not send add request, just click on the user to view his vcard.
4. Have a look at the log file to find the desired skypename.
The record will be like this for real user ip: -r184.108.40.206:31101
And like this for user internal network card ip: -l220.127.116.11
21:16:45.818 | T#3668 PresenceManager: | noticing skypetestuser1 0x3e54a539a91a19fc-s-s18.104.22.168:40013-r22.214.171.124:31101-l172 .10.5.17:22960 23d23109 82f328ff
5. Catch that skype user via whois service.
The mentioned steps will help you to get the following information about a skype user: City, Country, Internet provider and internal user ip-address.
Now, you can troll him about CIA and Mossad, he-he.
Skype version 5.5 is a hybrid of GUI on delphi and embedded dll with skype "kernel". This kernel is fully independent structure in binary code - code block, data block, imports. And it was built with use of VC compiler(exists VC lib signatures).
This kernel has not contain any reference to external code/data in delphi part. And only entry point block xrefs on kernel from delphi GUI. It can be saved as independent binary code with dll-header, and that kernel will work, i tested this.
skype14 -> skype14 skype14 -> skype3x skype14 -> skype4x skype14 skype5xSo there's no reason to work on a skype14.exe binary anymore. But it has received many patches for debugging reasons (analyzing connection and handshake flow) previously.
skype38 skype14 (no need for this anymore) skype38 -> skype3x skype38 -> skype4x skype38 -> skype5xThe bad thing is that (in skype38 and skype41) in many parts of code the debug info was removed and also code addresses and places changed a lot. I can not simply find an old part of code from skype14 in the new skype38 binary. So, almost all the hard work needs to be done again.