Linux Security and Troubleshooting
One should develop a security policy with the management team to protect
the the company and yourself. Typically, the misbelief is
that "security through obscurity" is acceptable.
- File Protections and Trojan Horses (setuid or setgid programs)
- Services
-
IP Security Protocol (IPSEC) - network layer security. Mandatory for
IPV6
- Network scanners: strobe
- Intrusion scanners: netssus
- Network based attack dectection:
NFR
- Packet sniffers: tcpdump,
snifft
Important configuration files:
- hosts.equiv & $HOME/.rhosts - specify hosts allowed by BSD r commands
- hosts.deny, hosts.allow - specify services allowed and deny by domaiISn
telnetd, ftpd: ALL # deny all
telnetd, ftpd: LOCAL, .origin.com # allow local and all the hosts in tacpa.org
- ftpusers - specify users not allowed to login via ftp
- securetty - specify which tty devices root is allowed to login on.
Troubleshooting
One cannot become an excellent troubleshooter overnight, but
with persistence and good motivation along with good
backup procedures, one can be indispensable in an organization.
Most of all, Unix guys/gulls ought to share
resources (such as IPO stocks :-) and knowledge with others.
There are many handy Linux
documentations,
as well as a good
search engine on the web.
To find out which commands to use based upon a keyWord, one can
enter "man -k keyWord".
In addition, many Unix commands provide on-line help.
To get a brief description of command usage and available options,
enter "command anyInvalidString".
System
- Bootable Floppy or Rescue Kit and Win95 Emergency Disk:
make a bootable floppy as soon as possible. Refers to
Upgrade
Kernel in session one. When systems hang during boot time,
you may boot Linux in single user mode (see session4.html) and
find out which daemon (started by a script under /etc/rc.d/init.d)
is causing problem. Under single user mode, you may mount
all the file sytems for troubleshoot. For redHat Linux, you may
press I to enter interactive startup and answer no to those
daemons that failed to start up.
You should also create an older version of
"Bootable Installation Floppy" such as Opelinux 1.3. It also allows
you to boot from the floppy and mount
the file system on of hard drive to recover damaged files or modify
root password. e.g.:
- chkconfig # display, activate, or de-activate init processes (redHat)
- hdparm -d1 /dev/hda
printer
-
parPort device: e.g. printer is a parPort device.
- cat /proc/dma
- cat /proc/interrupts
- cat /proc/tty/driver/serial
- cat /proc/ioports
Network
Besides the Ethernet interface card, your kernel should contain
a
network driver that matches with your adaptor. Without
recompiling a new kernel, you have to load the driver
modules with "insmod". (see sessioin1.html for more info.)
Multi-card also work on Linux.
Pcmcia driver
is required for laptops.
X
- XF86Config
- startx >& /tmp/x.out
- DISPLAY environment variable
- /usr/X11R6/lib/X11/doc/VideoModes.doc
- xauth and xhost
- $HOME/.Xsecurity
- /usr/X11R6/lib/X11/xdm/{xdm-config,xdm-error.log}
Note: the location of xdm-error.log is specified in xdm-config
References:
Linux Administrators Security Guide
Basic Linux Network Security
Linux Search
CERT
Security Software
Intrusion Detection Tools
Spoofing
Intrusion Detection
IPSec
Beyond Security
Linux's Tell-Tale Heart
Router Appliance
Linux in VPN
Firewall
FAQ
SecurityPortal
LogCheck
Firewall in Kernel 2.4
IPTables
OpenWall
Networking Security
SecurityArea
Security
Intrusion Detection
LinuxSecurity.com
IPtables Tutorial
NetFilter
ISP
Virus Writing