Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
both proftpd and wu-ftpd have an inetd wrapper, most distributions in my experience come with inetd (xinetd for red hat based distro's) already set up.
thats not excactly correct. inetd is the tcp-wrapper while programs such as proftpd, wu-ftpd, openssh, among others are capable of using tcp-wrappers. What a tcp-wrapper does is listen and accept connections to a port (generally 21 for ftp) and handle the connections. From there it forwards the data to the program (which isn't actually listening on any port, but listening to inetd). Hopefully I made that clear enough. The benefit of using tcp-wrappers, is you add another level of security to your program. With inetd in paticular it sends each connection through a series of tests, such as is this remote address in hosts.allow or hosts.deny? inetd is not the only tcpwrapper program, actually it has some major bugs such as it's "flaky" once it gets up to handleing 500+ concurrent connections. tcpserver by daniel j. bernstein is another more secure tcpwrapper that is commonly used.
from linuxgeek.net TCPwrappers
The tcpwrappers replace a number of "listening" daemons with a single "master" daemon
that listens for service requests for several common services on the system. When a
request for a service is made the tcpwrapper (tcpd) "wakes" the daemon for that service.
This does two things. It saves on system resources, since only one process needs to be
running. It also gives more fine grained control over who will be allowed to access
services through access control lists.
The daemons that tcpwrappers ``listens'' for are all servers listed in /etc/inetd.conf.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.