Inthe BitTorrent file distribution system, a torrent file or meta-info file is a computer file that contains metadata about files and folders to be distributed, and usually also a list of the network locations of trackers, which are computers that help participants in the system find each other and form efficient distribution groups called swarms.[1] Torrent files are normally named with the extension .torrent.
A torrent file acts like a table of contents (index) that allows computers to find information through the use of a BitTorrent client. With the help of a torrent file, one can download small parts of the original file from computers that have already downloaded it. These "peers" allow for downloading of the file in addition to, or in place of, the primary server. A torrent file does not contain the content to be distributed; it only contains information about those files, such as their names, folder structure, sizes, and cryptographic hash values for verifying file integrity.
The BitTorrent system has been created to ease the load on central servers, as instead of having individual clients fetch files from the server, BitTorrent can crowd-source the bandwidth needed for the file transfer and reduce the time needed to download large files. Many free/freeware programs and operating systems, such as the various Linux distributions offer a torrent download option for users seeking the aforementioned benefits. Other large downloads, such as media files, are often torrented as well.
Typically, Internet access is asymmetrical, supporting greater download speeds than upload speeds, limiting the bandwidth of each download, and sometimes enforcing bandwidth caps and periods where systems are not accessible. This creates inefficiency when many people want to obtain the same set of files from a single source; the source must always be online and must have massive outbound bandwidth. The BitTorrent protocol addresses this by decentralizing the distribution, leveraging the ability of people to network "peer-to-peer", among themselves.
Each file to be distributed is divided into small information chunks called pieces. Downloading peers achieve high download speeds by requesting multiple pieces from different computers simultaneously in the swarm. Once obtained, these pieces are usually immediately made available for download by others in the swarm. In this way, the burden on the network is spread among the downloaders, rather than concentrating at a central distribution hub or cluster. As long as all the pieces are available, peers (downloaders and uploaders) can come and go; no one peer needs to have all the chunks or to even stay connected to the swarm in order for distribution to continue among the other peers.
A small torrent file is created to represent a file or folder to be shared. The torrent file acts as the key to initiating downloading of the actual content. Someone interested in receiving the shared file or folder first obtains the corresponding torrent file, either by directly downloading it or by using a magnet link. The user then opens that file in a BitTorrent client, which automates the rest of the process. In order to learn the internet locations of peers who may be sharing pieces, the client connects to the trackers named in the torrent file, and/or achieves a similar result through the use of distributed hash tables. Then the client connects directly to the peers in order to request pieces and otherwise participate in a swarm. The client may also report progress to trackers, to help the tracker with its peer recommendations.
When the client has all the pieces, the BitTorrent client assembles them into a usable form. They may also continue sharing the pieces, elevating their status to that of seeder rather than an ordinary peer.
A torrent is uniquely identified by an infohash, a SHA-1 hash calculated over the contents of the info dictionary in bencode form. Changes to other portions of the torrent do not affect the hash. This hash is used to identify the torrent to other peers via DHT and to the tracker. It is also used in magnet links.
The new format uses SHA-256 in both the piece-hashing and the infohash, replacing the broken SHA-1 hash. The "btmh" magnet link would contain the full 32-byte hash, while communication with trackers and on the DHT uses the 20-byte truncated version to fit into the old message structure.[2] It is possible to construct a torrent file with only updated new fields for a "v2" torrent, or with both the old and new fields for a "hybrid" format. However, as a torrent would have different infohashes in v1 and v2 networks, two swarms would form, requiring special handling by the client to merge the two.[3]
A core feature of the new format is its application of merkle trees, allowing for 16KiB blocks of a piece to be individually verified and re-downloaded. Each file now always occupy whole piece sizes and have an independent merkle root hash, so that it's possible to find duplicate files across unrelated torrent files of any piece length. The file size is not reduced (assuming piece size stays the same; v2's tree structure allows larger pieces with fewer ill effects), but the info dictionary required for magnet links are (only in v2-only torrents).[3]
A torrent file can also contain additional metadata defined in extensions to the BitTorrent specification.[4] These are known as "BitTorrent Enhancement Proposals." Examples of such proposals include metadata for stating who created the torrent, and when.
These extensions have been deployed in one or more implementations as well as having been proven useful through consistent and widespread use. While they may require minor revisions, they are largely considered to be complete, only awaiting the blessing of Bram Cohen in order to be elevated to the status of Final/Active Process.
The specification recommends that nodes "should be set to the K closest nodes in the torrent generating client's routing table. Alternatively, the key could be set to a known good node such as one operated by the person generating the torrent."
Private torrents are to be used with a private tracker. Such a tracker restricts access to torrents it tracks by checking the peer's IP, refusing to provide a peer list if the IP is unknown. The peer itself is usually registered to the tracker via a gated online community; the private tracker typically also keep statistics of data transfer for use in the community.
Decentralized methods like DHT, PeX, LSD are disabled to maintain the centralized control. A private torrent can be manually edited to remove the private flag, but doing so will change the info-hash (deterministically), forming a separate "swarm" of peers. On the other hand, changing the tracker list will not change the hash. The flag does not offer true privacy, instead operating as a gentlemen's agreement.
In BEP-0017, a new key, httpseeds, is placed in the top-most list (i.e., with announce and info). This key's value is a list of web addresses where torrent data can be retrieved. Special server support is required. It remains at Draft status.
BEP-0030[10] extends BitTorrent to support Merkle trees (originally implemented in Tribler). The purpose is to reduce the file size of torrent files, which reduces the burden on those that serve torrent files.
Last year (2018) I was accused of torrenting Files whilst in my residence in Germany. I have never torrented any file ever. One thing that stands out is that during the same day CyberGhost (the VPN [paid license] provider I use) installed a plug-in in my computer approximately 5 hours before the time and place I am accused of the torrented files. Is it possible that this Plug-in used my IP address, or hacked into my personal information and an anonymous user committed the crime? I am now forced to pay a fine of 1000+ EUR or go to court. Can someone help me out here and provide me with sources/feedback to articles regarding this possibility? Any help is really appreciated because I do not dispose of the money to pay a fine for a crime I did not commit. Thank you all.
P2P itself is not illegal. German law considers that sharing content protected by copyright is illegal. You can share non-protected content, like let's say an .iso image of a public Linux distribution. Simply using P2P does not violate anything.
If they can prove that you did download copyright protected files, then yes, fines are possible, but not that easy. German courts have stated that the owner of the internet access is in theory responsible for any wrong-doings happening on that network and that it is their duty to secure them.
An IP address does not represent a person. Legally, an accusation based on IP-only does not stand. That IP can be hijacked by malware or another person can be behind the terminal using it when the offense is done.
The notice you got can be considered blackmail. I put it under blackmail because the letter is sent by law firms (that hire specialized third-party services that are scanning P2P nodes and clients, recording IP adresses that are currently downloading illegally in Germany, after which they are authorized by law to ask your internet provider to disclose any information linked to that IP adress), which in turn are hired by companies owning the copyrighted items. So it's a 3rd party involved. Basically, the letter is a warning to let you know that this 3rd party entity knows what you did and if you do not want to go to court you should pay a fine.
Conclusion: Ignoring it would be the recommended choice is this situation. You'll probably never hear from them again, unless you repeat the offense, in which case they will dig more into the matter and they could gather more evidence than (3), which will make the basics for a possible legal case. If you also received a document named "Unterlassungserklrung" you should not sign it as doing that would be an admission of guilt, which would give them a lot more legal ground to pursue things further.
3a8082e126