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.
as root, find out where ssh is: 'whereis ssh', then just add that directory (/sbin ?) to the path statement in erm.. etc/rc.local i think. I don't think that's the RIGHT way to add paths, but it works (assuming the path doesn't get re-written completely later on. might want to add it to /etc/profile instead.. up to you.
Uh. I think he means he wants to know how users can use the ssh service...
As admin, the only thing you need to provide for users to use ssh, is configuring and running the ssh daemon and checking your access restrictions if running behind a firewall, and/or tcpwrappers if run from (x)inetd. Make sure you understand the implications when configuring sshd options, besides from the different version issues.
As user they will "add" themselves to use ssh, they make a ~/subdir thatll hold their identity and config, generate the key and distribute the public part to the account on the other server.
If youre expecting a lot of new users, you might as well add examples to /etc/skel. Also make sure you're not providing r services, being able to rlogin defeats the purpose of ssh a bit...