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.
Hi guys, I'm currently in the midst of doing a bit of network admin, in preparation to go live in the near future. In the process, a good portion of that is hardening the server.
My question is: currently I have a user, ssh, that is the only user that can be sshed into. Idea being, it will be more secure. I want to set up this account with NO permissions, other than read/write from its home directory, and su to rootl1. The rootl1 account will be able to access the web server root directory, with read/write permissions, but cannot delete anything. This can su into rootl2, which can delete stuff, but everything is backed up before modifications. This can su into rootl3, and, well, you get the idea.
My question is, how can I make it so that accounts can only su into certain other accounts, and no others? So ssh can su into rootl1, but can only get to rootl2 by going through rootl1 (the idea being that if someone can get into ssh, they would need a bunch more passwords to be able to do anything bad).
The permission to write is the same as deleting, there is no difference in principle between these things.
You certainly can't do this with su, that's noa legitimate use of it. Your best bet is to look at sudo instead, and restrict their access that way. Don't allow the user to become anyone else, allow them to perform specific operations as another user. your multiple root princple sounds kinda... quirky... :s