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.
We have an amature group of Linux admin, and we recently had a break into our Linux system - and we have just re-install everything. We have a reverse problem however (unlike Goma_2's). We are currently able to login as root via telnet or ssh. How do we disable it ?
And how do we disable root login directly at the terminal ? We remember that we managed to have a configuration where root cannot login directly at the ternimal or remote. But we also set a 'special' user that can su root and grab 100% of root privilages, while all other user aren't given 100%. We just forget how to redo this.
muhazam, to configure from where root can log in, use the file /etc/securetty
here is an extract of mine:
# This file contains the device names of tty lines (one per line,
# without leading /dev/) on which root is allowed to login.
# for devfs:
if u want to configure who can use "su", do it in /etc/sudoers. do man sudoers for more info.
Hi muhazam, welcome to LQ, hope you enjoy it.
One note: next time please make your own new thread, that way you can ensure your question gets the attention it needs.
We are currently able to login as root via telnet or ssh. How do we disable it ?
SSH: sshd_config: the "PermitRootLogin" directive (amateur or not, if you don't stick with SSH defaults and also don't read the manuals, then there's little hope...)
Telnet: ditch it. Period.
If "root" needs physical access to the box, then allow one console: echo tty1 > /etc/securetty, else $>/etc/securetty to clean the file.
Hi, thanks for the responce from Mr....... unspawn ?
Editing the securetty file does not helps. Haven't tried the sshd_config yet either, coz..... yeah need to read manual first.
I think I can start making my own threads and there will be a lot of it later. For now (urgent) can anyone direct me to any page or website that list out each and everything that we must do to patch up all known possible security leak in a newly installed Linux ? Thanks.
NESSUS security scanner is said to be one of the TOP rated known security scanners available. The definitive security is prolly in many ways based upon what you have running on your system. However generally the streams would be
system used for connectiviity for larger net
points of interface with larger net
conditions for exchange for larger net
methods of exchange for larger net
data handling of conditions
next would be collatoral by mishap meaning closing off ability to perform functions beyond compromise or conditions of use.
If you examine each application from the kernel up you should be able to see the local usages and the larger net usages, at that point it is understanding what services are required or can be modified and what services perform to the function you required.
However there are allot of point of information on the net and new was of implementing things. However THE STANDARDS are all pretty basic by the time you understand the issues you should be able to modify the code to remove or neuter usages that are not optimal.
as for a full listing I havnt seen a central database yet however there are a large number of sites that address many .