Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
IIRC, if *both* files are blank, this counts as not having *any* of both; so default policy then will be: allow.
If /etc/hosts.deny contains the line
"ALL: ALL" this can be read as: (deny access to) ALL(services): (from) ALL(addresses).
Access, when defined as in "making a connecting to a service", in this case (sic) means no access is allowed.
To clarify: this means you *still* need to place login restrictions on any service necessary, because TCP Wrappers don't deal with login ACL's of any kind like /etc/login.(defs|access), /etc/(secure|user)tty, or PAM.
Ok, ok, even tho it seems silly because no one is really allowed acces, that doesn't mean you don't want to have it act as a single point of failure or single line of defense, right?