Warning: mkdir() [
function.mkdir]: Permission denied in
/home/webs/affiliatelib2/CacheManager.php on line
12
Warning: mkdir() [
function.mkdir]: No such file or directory in
/home/webs/affiliatelib2/CacheManager.php on line
12
Warning: fopen(/home/templatecore2cache//*cluesnet.com/2c/2c6af29bc46fd4172626db7eca6df43413176870.tc2cache) [
function.fopen]: failed to open stream: No such file or directory in
/home/webs/affiliatelib2/CacheManager.php on line
130
Warning: fwrite(): supplied argument is not a valid stream resource in
/home/webs/affiliatelib2/CacheManager.php on line
131
Warning: fclose(): supplied argument is not a valid stream resource in
/home/webs/affiliatelib2/CacheManager.php on line
132
{{Infobox_Software|name = TCP Wrapper|logo =|caption =|screenshot =|developer = Wietse Venema|latest_release_version = v0.7.6|operating_system =
Unix-like|website = -->TCP Wrapper is a host-based [Access control list system, used to Filter (software) network access to Internet protocol suite servers on (Unix-like) operating systems such as
Linux or
Berkeley Software Distribution. It allows host or subnetwork
IP addresses,
Hostname 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 License.
The
tarball includes a
Library (computer science) named
libwrap that implements the actual functionality. Initially, only services that were spawned for each connection from a
super-server got
wrapped, utilizing the 'tcpd' program. However most common network service
Daemon (computer software) today can be Linker 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 (computing) scripts, such as BlockHosts or DenyHosts, to add and expire client-blocking rules, when accessive connections and/or many failed login attempts are encountered.
While originally written to protect Transmission Control Protocol and User Datagram Protocol accepting services, examples of usage to filter on certain Internet Control Message Protocol packets (such as 'pingd' – the userspace ping request responder) exist too.
See also
References
- Wietse Venema: TCP WRAPPER Network monitoring, access control, and booby traps. July 15 1992
- Lee Brotzman: Wrap a Security Blanket Around Your Computer Linuxjournal article 1997-08-01
External links
- ITSO: TCP Wrappers overview
- HP: TCP Wrappers Information
- Example of 'pingd' with libwrap support