TCP Wrapper

TCP Wrapper is a host-based Networking ACL system, used to filter network access to Internet Protocol servers on (Unix-like) operating systems such as Linux or BSD. It allows host or subnetwork IP addresses, names and/or ident query replies, to be used as tokens on which to filter for access control purposes.

The original code was written by Wietse Venema at the Eindhoven University of Technology, The Netherlands, between 1990 and 1995. As of June 1, 2001 the program is released under its own BSD-style license.

The tarball includes a library named libwrap that implements the actual functionality. Initially, only services that were spawned for each connection from a super-server (such as inetd) got wrapped, utilizing the tcpd program. However most common network service daemons today can be linked against libwrap directly. This is used by daemons that operate without being spawned from a super-server, or when a single process handles multiple connections. Otherwise, only the first connection attempt would get checked against its ACLs.

When compared to host access control directives often found in daemons' configuration files, TCP Wrappers have the benefit of runtime ACL reconfiguration (i.e. services don't have to be reloaded or restarted) and a generic approach to network administration.

This makes it easy to use for anti-Worm scripts, such as BlockHosts, DenyHosts or Fail2ban, to add and expire client-blocking rules, when excessive connections and/or many failed login attempts are encountered.

While originally written to protect TCP and UDP accepting services, examples of usage to filter on certain ICMP packets (such as 'pingd' – the userspace ping request responder) exist too.

The fourth P2P-Generation

Streams over P2P

Apart from the traditional file sharing there are services that send streams instead of files over a P2P network. Thus one can hear radio and watch television without any server involved -- the streaming media is distributed over a P2P network. It is important that instead of a treelike network structure, a swarming technology known from BitTorrent is used. Best examples are Peercast, Miro, Cybersky and demo TV.

General

* Broadcatching
* Podcast

Tree structure

* CoolStreaming
* Peercast

Swarm structure such as BitTorrent

* Djingle
* Icecast
* Joost
* MediaBlog
* PeerCast
* PPLive
* PPStream
* SopCast
* TVUPlayer
* Vuze

Third P2P-Generation

indirect and encrypted

The third generation of peer-to-peer networks are those that have anonymity features built in. Examples of anonymous networks are ANts P2P, RShare, Freenet, I2P, GNUnet and Entropy.

A degree of anonymity is realized by routing traffic through other users' clients, which have the function of network nodes. This makes it harder for someone to identify who is downloading or who is offering files. Most of these programs also have strong encryption to resist traffic sniffing.

Friend-to-friend networks only allow already-known users (also known as "friends") to connect to the user's computer, then each node can forward requests and files anonymously between its own "friends'" nodes.

Third-generation networks have not reached mass usage for file sharing because most current implementations incur too much overhead in their anonymity features, making them slow or hard to use. However, in countries where very fast fiber-to-the-home Internet access is commonplace, such as Japan, a number of anonymous file-sharing clients have already reached high popularity.

An example might be: Petra gives a file to Oliver, then Oliver gives the file to Anna. Petra and Anna thus never become acquainted and thus are protected. Often used virtual IP addresses obfuscate the user's network location because Petra only knows the virtual IP of Anna. Although real IP's are always necessary to establish a connection between Petra and Oliver, nobody knows if Anna really requested and Petra really send the file or if they just forward it (As long as they won't tell anyone their virtual IP's!). Additionally all transfers are encrypted, so that even the network administrators cannot see what was sent to whom. Example software includes WASTE, JetiANts, Tor and I2P. These clients differ greatly in their goals and implementation. WASTE is designed only for small groups and may therefore be considered Darknet; ANts and I2P are public Peer-to-Peer systems, with anonymization provided exclusively by routing reach.

Ants network

* ANts P2P
* JetiANts
* Hornet

Mute network

* MUTE
* Kommute - KDE

I2P network

* I2P
* I2Phex - Gnutella over I2P
* iMule - eDonkey (Kademlia) over I2P
* Azureus - has I2P plugin

Retroshare-Network (F2F Instant Messenger)

* Retroshare Instant Messenger - Retroshare Chat Messenger for privacy of filesharing

other networks or clients

* Alliance
* Freenet
* GNUnet
* Nodezilla
* OFF System
* Perfect Dark
* Proxyshare
* RShare
* Share
* Tor
* WinNY
* Zultrax

Second P2P-Generation

Decentralization

After Napster encountered legal troubles, Justin Frankel of Nullsoft set out to create a network without a central index server, and Gnutella was the result. Unfortunately, the Gnutella model of all nodes being equal quickly died from bottlenecks as the network grew from incoming Napster refugees. FastTrack solved this problem by having some nodes be 'more equal than others'.

By electing some higher-capacity nodes to be indexing nodes, with lower capacity nodes branching off from them, FastTrack allowed for a network that could scale to a much larger size. Gnutella quickly adopted this model, and most current peer-to-peer networks implement this design, as it allows for large and efficient networks without central servers.

Also included in the second generation are distributed hash tables (DHTs), which help solve the scalability problem by electing various nodes to index certain hashes (which are used to identify files), allowing for fast and efficient searching for any instances of a file on the network. This is not without drawbacks; perhaps most significantly, DHTs do not directly support keyword searching (as opposed to exact-match searching).

The best examples are Gnutella, Kazaa or eMule with Kademlia, whereby Kazaa has still a central server for logging in. eDonkey2000/Overnet, Gnutella, FastTrack and Ares Galaxy have summed up approx. 10.3 million users (as of April 2006, according to slyck.com). This number does not necessarily correspond to the actual number of persons who use these networks; it must be assumed that some use multiple clients for different networks.

Multi-Network-Clients

Further networks or clients

File sharing

File sharing refers to the providing and receiving of digital files over a network, usually following the peer-to-peer (P2P) model, where the files are stored on and served by personal computers of the users. Most people who engage in file sharing on the Internet both provide (upload) files and receive files

P2P file sharing is distinct from file trading in that downloading files from a P2P network does not require uploading, although some networks either provide incentives for uploading such as credits or forcing the sharing of files being currently downloaded.

USENET was the first global file sharing network. Files are posted to alt.binary.* groups by users and copies are propagated to all hosts that carry that particular group. Unlike the later peer-to-peer file sharing networks, requests for a file relies on people asking others to post them, and users save them if they want those files.

First P2P-generation: Server-client

The first generation of peer-to-peer file sharing networks had a centralized server system. This system controls traffic amongst the users. The servers store directories of the shared files of the users and are updated when a user logs on. In the centralized peer-to-peer model, a user would send a search to the centralized server of what they were looking for. The server then sends back a list of peers that have the data and facilitates the connection and download. The Server-Client system is quick and efficient because the central directory is constantly being updated and all users had to be registered to use the program. However, there is only a single point of entry, which could result in a collapse of the network. In addition, it is possible to have out of date information or broken links if the server is not refreshed.

The first file-sharing programs marked themselves by inquiries to a server, either the data to the download held ready or in appropriate different Peers and so-called Nodes further-obtained, so that one could download there. Two examples were Napster (today using a pay system) and eDonkey2000 in the server version (today, likewise with Overnet and KAD - network decentralized). Another notable instance of peer to peer file sharing, which still has a free version, is Limewire.

File hosting service

A file hosting service, online file storage service, or online media center is an Internet hosting service specifically designed to host static content, typically large files that are not web pages. Typically they allow web and FTP access. They can be optimized for serving many users (as is implied by the term "hosting") or be optimized for single-user storage (as is implied by the term "storage"). Related services are video sharing, virtual storage and remote backup.

Software file hosting

Shareware authors often use file hosting services to serve their software. The inherent problem with free downloads is the huge bandwidth cost. These hosts also offer additional services to the authors such as statistics or other marketing features.

Personal file storage

Personal file storage services are aimed at private individuals, offering a sort of "network storage" for personal backup, file access, or file distribution. Users can upload their files and share them publicly or keep them password-protected.

Prior to the advent of personal file storage services, off-site backup services were not typically affordable for individual and small office computer users.

Sometimes people prefer hosting their files on a publicly accessible HTTP server. In this case, they generally choose paid hosting, and use their hosting for this purpose. Many free hosting providers do not allow the storage of files for non-website-related use.

Content caching

Content providers who potentially encounter bandwidth congestion issues may use services specialized in distributing cached or static content. It is the case for companies with a major Internet presence.