Misplaced Pages

TCP Wrappers: Difference between revisions

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
Browse history interactively← Previous editNext edit →Content deleted Content addedVisualWikitext
Revision as of 13:54, 22 September 2006 edit70.184.226.137 (talk) External links← Previous edit Revision as of 15:19, 22 September 2006 edit undoHaakon (talk | contribs)Extended confirmed users13,007 editsm rv linkspamNext edit →
Line 47: Line 47:
* *
* *

* - vBulletin Optmizing Tips
</div> </div>



Revision as of 15:19, 22 September 2006

TCP Wrapper
Developer(s)Wietse Venema
Stable releasev0.7.6
Operating systemUnix-like
TypeSecurity
LicenseBSD
Website

TCP Wrapper is a host-based network ACL system, used to filter network access to Internet protocol services run on (Unix-like) operating systems such as Linux or BSD. It allows host or subnetwork IP adresses, names and/or ident query replies, to be used as tokens on which to filter for access control purposes. The name Wrapper is a reference to the wrapper design pattern (of the 'tcpd' program included).

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 start 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, and thus honor TCP Wrapper ACLs even when in stand-alone operating mode.

Over 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.

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.

Services that grab the socket after being started by a super-server (for performance reasons on consecutive connects – usually multithreaded applications such as: Peter Anvin's tftpd and Peter Eriksson's identd), have to be linked against libwrap rather than wrapped (by tcpd, xinetd, or similar) as otherwise only the first connection attempt gets checked against its ACLs.

The project is usually referred to as TCP Wrappers and is named tcp-wrappers in the Gentoo Linux portage package repository. In Gentoo Linux TCP Wrappers is enabled with the 'tcpd' use-flag.

See also

References

External links

Categories: