BitTorrent Based DNS To Counter US Domain Seizures The domain seizures by the United States authorities in recent days and upcoming legislation that could make similar takeovers even easier in the future, have inspired a group of enthusiasts to come up with a new, decentralized and BitTorrent-powered DNS system. This system will exchange DNS information through peer-to-peer transfers and will work with a new .p2p domain extension. In a direct response to the domain seizures by US authorities during the last few days, a group of established enthusiasts have started working on a DNS system that can’t be touched by any governmental institution. Ironically, considering the seizure of the Torrent-Finder meta-search engine domain, the new DNS system will be partly powered by BitTorrent. In recent months, global anti-piracy efforts have increasingly focused on seizing domains of allegedly infringing sites. The Dot-P2P project was literally started a few days ago, but already the developers are making great progress.
eDonkey network The eDonkey Network (also known as the eDonkey2000 network or eD2k) is a decentralized, mostly server-based, peer-to-peer file sharing network best suited to share big files among users, and to provide long term availability of files. Like most sharing networks, it is decentralized, as there is not any central hub for the network; also, files are not stored on a central server but are exchanged directly between users based on the peer-to-peer principle. Currently, the eD2k network is not supported by any organization (in the past it was supported by the MetaMachine Corporation, its creator, which now is out of business) and development and maintenance is being fully provided by its community and client developers. There are many programs that act as the client part of the network. The original eD2k protocol has been extended by subsequent releases of both eserver and eMule programs, generally working together to decide what new features the eD2k protocol should support. Features[edit]
Truly Decentralized BitTorrent Downloading Has Finally Arrived BitTorrent is branded as a peer-to-peer technology, but despite this label the downloading process still relies heavily on central servers. In the first place there are the BitTorrent search engines and indexes such as The Pirate Bay and isoHunt. These are needed to search for content and to grab the .torrent file one needs to download a file. Besides these torrent sites, most BitTorrent downloads are still managed by so-called trackers. Finally central servers are used by moderators to help hunt spam and malware. In the last years these ‘central server’ vulnerabilities have caused a number of minor inconveniences for torrent users. To address these issues, ideally BitTorrent downloads should no longer require a central server. The latest version of the Tribler BitTorrent client (Win, Mac and Linux), released only a few minutes ago, is capable of all the above and many more things that could be described as quite revolutionary. Triber: search, download and play (large). Tribler Channels
File Transfer Protocol FTP is built on a client-server architecture and uses separate control and data connections between the client and the server.[1] FTP users may authenticate themselves using a clear-text sign-in protocol, normally in the form of a username and password, but can connect anonymously if the server is configured to allow it. For secure transmission that hides (encrypts) the username and password, and encrypts the content, FTP is often secured with SSL/TLS ("FTPS"). SSH File Transfer Protocol ("SFTP") is sometimes also used instead, but is technologically different. History[edit] The original specification for the File Transfer Protocol was written by Abhay Bhushan and published as RFC 114 on 16 April 1971. Protocol overview[edit] Communication and data transfer[edit] Illustration of starting a passive connection using port 21 The server responds over the control connection with three-digit status codes in ASCII with an optional text message. ASCII mode: used for text. Login[edit] Syntax[edit] or:
OneSwarm: The Privacy Aware BitTorrent Client Developed at the University of Washington, OneSwarm is a BitTorrent client that allows users to share files "anonymously" or with a specific group of friends. These features give users more control over their privacy, while maintaining a decent download speed. The client operates from within an Internet browser and is available for Mac, Windows and Linux. Those who’ve been reading TorrentFreak for long enough may remember how the MPAA and RIAA accused a printer at the University of Washington of copyright infringement a few years ago. With their research, the researchers pointed out that gathering evidence on BitTorrent downloaders is full of pitfalls. Perhaps not coincidentally the same research group is also behind the “privacy preserving” BitTorrent client OneSwarm, currently developed by Tomas Isdal and Michael Piatek, two PhD students at the University of Washington. Unlike other regular BitTorrent clients, OneSwarm allows users to share files only with a selected group of friends.
Gnutella2 History[edit] In November 2002, Michael Stokes announced the Gnutella2 protocol to the Gnutella Developers Forum. While some thought the goals stated for Gnutella2, primarily to make a clean break with the gnutella 0.6 protocol and start over so that some of gnutella's less clean parts would be done more elegantly, to be impressive and desirable, other developers, primarily those of LimeWire and BearShare, thought it a "cheap publicity stunt" and discounted technical merits. Many still refuse to refer to the network as "Gnutella2" and instead refer to it as "Mike's Protocol" ("MP").[2] With the developers entrenched in their positions, a flame war soon erupted, further cementing both sides' resolve.[3][4][5][6] The draft specifications were released on March 26, 2003, and more detailed specifications soon followed. Design[edit] Gnutella2 relies extensively on UDP, rather than TCP, for searches. Protocol features[edit] Differences from gnutella[edit] Protocol[edit] Search algorithm[edit]
Researchers Improve BitTorrent Download Speeds Researchers from the Tribler project at Delft University of Technology are proposing a new set of rules that should significantly improve the download speeds of many BitTorrent users. The new "Superior Seeding Standard" implemented in the latest release of the Tribler BitTorrent client is inspired by the ratio-enforcement policies at private tracker communities, but doesn't discriminate against people with low bandwidth connections. Some scientists devote their lives to finding a cure for terminal illnesses, others hope to discover new planets in galaxies far away, but there’s also a group of scientists mostly concerned with improving BitTorrent. The Tribler team at Delft University of Technology are such a group, and they have found a way to improve download speeds for BitTorrent users who are committed to sharing. Tribler’s BitTorrent client has been in development for more than 5 years and continues to deliver experimental improvements and innovative ideas. The Paper
Hypertext Transfer Protocol The Hypertext Transfer Protocol (HTTP) is an application protocol for distributed, collaborative, hypermedia information systems.[1] HTTP is the foundation of data communication for the World Wide Web. The standards development of HTTP was coordinated by the Internet Engineering Task Force (IETF) and the World Wide Web Consortium (W3C), culminating in the publication of a series of Requests for Comments (RFCs), most notably RFC 2616 (June 1999), which defined HTTP/1.1, the version of HTTP most commonly used today. In June 2014, RFC 2616 was retired and HTTP/1.1 was redefined by RFCs 7230, 7231, 7232, 7233, 7234, and 7235.[2] HTTP/2 is currently in draft form. Technical overview[edit] URL beginning with the HTTP scheme and the WWW domain name label. A web browser is an example of a user agent (UA). HTTP is designed to permit intermediate network elements to improve or enable communications between clients and servers. History[edit] The first documented version of HTTP was HTTP V0.9 (1991).
BitTorrent Pirates Go Nuts After TV Release Groups Dump Xvid Some Internet piracy groups decided to implement some new regulations and standards last week. Instead of releasing TV shows in the Xvid/avi format, groups responsible for putting major TV shows online switched to MP4/x264. Outraged by the lack of democracy, some BitTorrent users are directing their anger at bewildered torrent sites and even threatening to boycott releases. Every now and again, the world’s most famous piracy release groups get together and have a big old meeting to decide how they’ll carry out their future activities. Ok, so the last sentence isn’t true, but nevertheless that appears to be the current assessment of events according to some BitTorrent users. The problem stems back to a new document which details a set of standards TV show release groups such as LOL and MOMENTUM will have to live up to in order to comply with so-called ‘Scene rules’. “x264 has become the most advanced video codec over the past few years. “LOL, why are all your new uploads MP4 format?
Gnutella Gnutella (/nʌˈtɛlə/ with a silent g, but often /ɡnʌˈtɛlə/) (possibly by analogy with the GNU Project) is a large peer-to-peer network. It was the first decentralized peer-to-peer network of its kind, leading to other, later networks adopting the model.[1] It celebrated a decade of existence on March 14, 2010 and has a user base in the millions for peer-to-peer file sharing. In June 2005, gnutella's population was 1.81 million computers[2] increasing to over three million nodes by January 2006.[3] In late 2007, it was the most popular file sharing network on the Internet with an estimated market share of more than 40%.[4] History[edit] The first client was developed by Justin Frankel, Gianluca Rubinacci and Tom Pepper of Nullsoft in early 2000, soon after the company's acquisition by AOL. The next day, AOL stopped the availability of the program over legal concerns and restrained Nullsoft from doing any further work on the project. Design[edit] The gnutella search and retrieval protocol
New Data Exposes BitTorrent Throttling ISPs New data published by the Google-backed Measurement Lab gives a unique insight into the BitTorrent throttling practices of ISPs all over the world. In the U.S. and Australia most large ISPs limit less than 10 percent of BitTorrent transfers. In the UK and Canada on the other hand, some providers interfere with up to three-quarters of all BitTorrent traffic. New data collected by Measurement Lab (M-Lab) shows how frequently Internet providers limit torrent traffic. Previously the researchers published data up until 2010, and now the results have been updated to include the first quarter of 2012. United States BitTorrent throttling in the US is not as prevalent as it used to be. As a result of this ruling, the throttling percentage took a dive from nearly 50 percent to only 3 percent in 2010. Throttling was also greatly reduced at Charter over the last year, from 11 percent down to 4 percent. Worst: Cox (6%) Best: Comcast, Verizon, AT&T and others (3%) Worst: BT (65%) Best: O2 (2%) Canada
HTTP Secure Hypertext Transfer Protocol Secure (HTTPS) is a communications protocol for secure communication over a computer network, with especially wide deployment on the Internet. Technically, it is not a protocol in and of itself; rather, it is the result of simply layering the Hypertext Transfer Protocol (HTTP) on top of the SSL/TLS protocol, thus adding the security capabilities of SSL/TLS to standard HTTP communications. The security of HTTPS is therefore that of the underlying TLS, which uses long term public and secret keys to exchange a short term session key to encrypt the data flow between client and server. An important property in this context is perfect forward secrecy (PFS), so the short term session key cannot be derived from the long term asymmetric secret key; however, PFS is not widely adopted.[1] To guarantee one is talking to the partner one wants to talk to, X.509 certificates are used. Overview[edit] HTTPS creates a secure channel over an insecure network. Technical[edit]