Are you an EPFL student looking for a semester project?
Work with us on data science and visualisation projects, and deploy your project as an app on top of Graph Search.
Concept
FastTrack
Summary
FastTrack is a peer-to-peer (P2P) protocol that was used by the Kazaa, Grokster, iMesh and Morpheus programs. FastTrack was the most popular file sharing network in 2003, and used mainly for the exchange of music mp3 files. The network had approximately 2.4 million concurrent users in 2003. It is estimated that the total number of users was greater than that of Napster at its peak.
The FastTrack protocol and Kazaa were created and developed by Estonian programmers of BlueMoon Interactive headed by Jaan Tallinn, the same team that later created Skype. After selling it to Niklas Zennström from Sweden and Janus Friis from Denmark, it was introduced in March 2001 by their Dutch company Consumer Empowerment. It appeared during the end of the first generation of P2P networks – Napster shut down in July of that year. There are three FastTrack-based networks, and they use mutually incompatible versions of the protocol. The most popular clients on each are Kazaa (and its variations), Grokster, and iMesh. For more information about the various lawsuits surrounding Kazaa and Sharman Networks, see Kazaa.
FastTrack uses supernodes to improve scalability.
To allow downloading from multiple sources, FastTrack employs the UUHash hashing algorithm. While UUHash allows very large to be checksummed in a short time, even on slow weak computers, it also allows for massive corruption of a file to go unnoticed. Many people, as well as the RIAA, have exploited this vulnerability to spread corrupt and fake files on the network.
The FastTrack protocol uses encryption and was not documented by its creators. The first clients were all closed source software. However, initialization data for the encryption algorithms is sent in the clear and no public key encryption is used, so reverse engineering was made comparatively easy. In 2003, open source programmers succeeded in reverse-engineering the portion of the protocol dealing with client-supernode communication, but the supernode-supernode communication protocol remains largely unknown.
The
Official source
About this result
This page is automatically generated and may contain information that is not correct, complete, up-to-date, or relevant to your search query. The same applies to every other page on this website. Please make sure to verify the information with EPFL's official sources.