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.
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 a system on which I've successfully chrooted a number of users. However, since the users are chrooted, they obviously don't have access to the /etc directory (the real one) to change their passwords if need be. I want users to be able to do this. Has anyone else set up a system that allows this? I was thinking of just writing a custom "password change daemon" that could handle password change requests for chrooted users, but was wondering if anyone has a more elegant solution.
Let the users update a local (chroot) /etc/passwd and /etc/shadow then set up a script to move the single line for the users ID from the local /etc/shadow file to the real /etc/shadow. The only downside is the real password update will be delayed, so the user may need to use the old password until the update run.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
