Talk:Skype protocol: Difference between revisions
Line 28: | Line 28: | ||
Can someone who knows please add a section listing implementations? I'm not talking about wrappers around the Skype binary client, but actual new code. The official client is obviously an implementation, it appears ++skype may also be one. Are there any others? |
Can someone who knows please add a section listing implementations? I'm not talking about wrappers around the Skype binary client, but actual new code. The official client is obviously an implementation, it appears ++skype may also be one. Are there any others? |
||
: I'm not really sure what ++skype is. Is it just a wrapper? I'm not aware of any other implementations, but would also be interested to know if anyone has started a GPL project. [[User:Pgr94|Pgr94]] 17:14, 27 May 2007 (UTC) |
: I'm not really sure what ++skype is. Is it just a wrapper? I'm not aware of any other implementations, but would also be interested to know if anyone has started a GPL project. [[User:Pgr94|Pgr94]] 17:14, 27 May 2007 (UTC) |
||
:: According to [[User |
:: According to [[User:217.162.207.65]] "++Skype library is a library for the API of the software and not for the network." [[User:Pgr94|Pgr94]] 09:51, 18 June 2007 (UTC) |
||
==Fair use rationale for Image:Skype logo.png== |
==Fair use rationale for Image:Skype logo.png== |
Revision as of 09:51, 18 June 2007
Tools used
Baset and Schulzrinne used:
Biondi and Desclaux used:
- PytStop to circumvent checksums
- Skype checks for SoftICE to prevent debugging. However RR0d debugger works.
- Scapy interactive packet manipulation program
- shellcode Oracle Revelator in Shellforge
- IPQUEUE
- SIRINGE
- Skypy : a scapy wrapper to reassemble and decode obfuscated TCP streams (not released?)
Techniques used to defend the Skype binary
Skype relies heavily on code obfuscation:
- Much of the skype binary is encrypted. It provides its own unpacker which erases the original import table as it is loaded.
- Code integrity checksums, executed randomly, and obfuscated with random lengths and random operators
- Anti-debuggers
- attempt to identify breakpoints and trap the debugger.
- target specific debuggers by checking for certain loaded drivers
- General code obfuscation with fake error handlers that directly manipulate memory and registers. —The preceding unsigned comment was added by Pgr94 (talk • contribs) 14:11, 7 December 2006 (UTC).
Skype protocol implementations
Can someone who knows please add a section listing implementations? I'm not talking about wrappers around the Skype binary client, but actual new code. The official client is obviously an implementation, it appears ++skype may also be one. Are there any others?
- I'm not really sure what ++skype is. Is it just a wrapper? I'm not aware of any other implementations, but would also be interested to know if anyone has started a GPL project. Pgr94 17:14, 27 May 2007 (UTC)
- According to User:217.162.207.65 "++Skype library is a library for the API of the software and not for the network." Pgr94 09:51, 18 June 2007 (UTC)
Fair use rationale for Image:Skype logo.png
Image:Skype logo.png is being used on this article. I notice the image page specifies that the image is being used under fair use but there is no explanation or rationale as to why its use in this Wikipedia article constitutes fair use. In addition to the boilerplate fair use template, you must also write out on the image description page a specific explanation or rationale for why using this image in each article is consistent with fair use.
Please go to the image description page and edit it to include a fair use rationale. Using one of the templates at Wikipedia:Fair use rationale guideline is an easy way to insure that your image is in compliance with Wikipedia policy, but remember that you must complete the template. Do not simply insert a blank template on an image page.
If there is other other fair use media, consider checking that you have specified the fair use rationale on the other images used on this page. Note that any fair use images uploaded after 4 May, 2006, and lacking such an explanation will be deleted one week after they have been uploaded, as described on criteria for speedy deletion. If you have any questions please ask them at the Media copyright questions page. Thank you.BetacommandBot 05:53, 6 June 2007 (UTC)