SlackwareThis Forum is for the discussion of Slackware Linux.
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.
I have question about what commands should be removed from regular user access, even though they are located in places such as /usr/bin/, /bin/ and a few other locations. What are some commands that you guys recommend normal users having limited access to?
My reason for posting this here, instead of security is that I'm basing this off of my slack install and would like to know what fellow slackers think of the commands readily available to users.
My solution to this potiental security risks to write a script that will create a new folder that would allow access only to higher privilaged users in a specified group without making things overly complicated. I plan on soft linking all the commands to a folder that allows a specific group to access, then further creating sub directories and groups to access specific commands like networking, root access and development tools.
I'm not a security expert(nor a slackware expert), but most commands that can seriously mess up a system will require root acess. I've set up sudoers, and changed my path to that of root(my personal machine, not multiple logins). Linux is pretty secure on it's own...sorry I can't be of more help.
My whole point to something like this, (and now I think about maybe a totally invalid one), is to have some sort of fall back for myself in case I allow some random users on to my machine and get screwed because of it. If they can't compile a program or telnet or ftp using my box as a jump point, I'd feel safer.
assuming the user does not own the build directory, then cannot compile anything. SSH is more secure than telnet, but if you don't want people logging in remotely, disable both. As for FTP, I don't know a whole lot about it, but again, if you don't need it, disable it