This article has not yet been rated on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | |||||||||||
|
124.197.18.179 22:29, 28 June 2007 (UTC)
Baset and Schulzrinne used:
Biondi and Desclaux used:
Skype relies heavily on code obfuscation:
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?
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)
start 2. send UDP packet(s) to HC 3. if no response within 5 seconds then 4. attempt TCP connection with HC 5. if not connected then 6. attempt TCP connection with HC on port 80 (HTTP) 7. if not connected then 8. attempt TCP connection with HC on port 443 (HTTPS) 9. if not connected then 10. attempts++ 11. if attempts==5 then 12. fail 13. else 14. wait 6 seconds 15. goto step 2
seems incorrect
attempts not initialized. --Sylvestersteele (talk) 08:52, 2 June 2009 (UTC)
77.215.46.17 (talk) 23:06, 3 April 2010 (UTC)
The obfuscated Skype RC4 key expansion algorithm has been leaked and is available in portable C code.[1] Code is available here: http://cryptolib.com/ciphers/skype/ pgr94 (talk) 19:00, 12 May 2011 (UTC)
in 2003 MS made an AntiTrust Settlement, in which they told to publish a lot of interoperability data, including "proprietary communications protocols". I bet Skype protocol fals into the definition ? i wonder if someone would push Microsoft into making the protocol public. 79.111.223.5 (talk) 20:00, 14 May 2011 (UTC)
There is news [2], that guy called Efim Bushmanov reverse engineered Skype protocol. — Preceding unsigned comment added by 83.26.113.233 (talk) 13:10, 3 June 2011 (UTC)
It would certainly be quite legal to reverse engineer in any european country, provided it was to create a new interoperating program (for example a 3rd party 'skype format compatible' application), and that did not make direct use of any de-compiled source-code. Reading such dis-assembled source code for inspiration, and then coming up with near identical code could probably be found illegal as would distributing it for others to do so. However reading it and coming up with some fully original work that was quite different but incidentally functionally interoperable or equivalent would not be a problem, neither would distributing it to others to read and do the same. Publishing decompiled source code for others to do with as they may is (!) a case for the well paid lawyer and his expert witness, and then publishing accross national boundries is another game again. Mike (in the UK!). — Preceding unsigned comment added by 109.207.29.2 (talk) 15:53, 26 September 2011 (UTC)
Hello fellow Wikipedians,
I have just added archive links to one external link on Skype protocol. Please take a moment to review my edit. If necessary, add ((cbignore))
after the link to keep me from modifying it. Alternatively, you can add ((nobots|deny=InternetArchiveBot))
to keep me off the page altogether. I made the following changes:
When you have finished reviewing my changes, please set the checked parameter below to true to let others know.
This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template ((source check))
(last update: 5 June 2024).
Cheers.—cyberbot IITalk to my owner:Online 00:58, 18 January 2016 (UTC)
According to the article at its present state, "In 2012, Microsoft altered the design of the network, and brought all supernodes under their control", and "Supernodes relay communications on behalf of two other clients". This would appear to suggest that if all packets produced by Skype after this change would go to Microsoft. However, Microsoft told this tech magazine (in Danish, sorry) that indeed packets still travel from peer to peer directly, a claim which is backed up by the magazine's own Wireshark testing. Perhaps something else is meant in the Wikipedia article, but in that case, I think that the current wording is misleading. --pred (talk) 10:08, 13 February 2016 (UTC)
It is my understanding that clients contact Skype relays in order to obtain IP addresses and port numbers for other clients. Clients then establish connections and sent packets directly to one another under a P2P architecture. The current intro says Skype is a client-server protocol, so this seems even more misleading. See this textbook around page 352, though it is possible it contains outdated information. Kreidy (talk) 22:48, 6 March 2019 (UTC)
None of the domain names in the list under the section Login is actually current. Either the new ones should be found and posted or they should be removed. --Ispanesach (talk) 16:14, 13 March 2018 (UTC)
The entire article is talking about the original classic Skype protocol which has long been deprecated and is no longer used however it's only reflected in the header: "The new Skype protocol—Microsoft Notification Protocol 24". I guess the article must be renamed and updated to reflect the status quo. Artem S. Tashkinov (talk) 15:01, 8 June 2020 (UTC)