Visit Jeremy's Blog.
Go Back > Forums > Linux Forums > Linux - Security
User Name
Linux - Security This forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.


Closed Thread
  Search this Thread
Old 02-13-2003, 04:00 PM   #1
Registered: May 2001
Posts: 28,886
Blog Entries: 55

Rep: Reputation: 3356Reputation: 3356Reputation: 3356Reputation: 3356Reputation: 3356Reputation: 3356Reputation: 3356Reputation: 3356Reputation: 3356Reputation: 3356Reputation: 3356
Security references

Welcome to the LQ Security references!

Securing a Linux box is not hard, but requires a bit of reading and planning ahead to make sure you covered the important points. That's why I compiled a few lists of texts about Linux security, grouped by subject:

1: Basics, important sites, HOWTO's, handbooks, tips, advisories, mailinglists, hardening, log analysis, sites, books
2: Netfilter, firewall, Iptables, Ipchains, DoS, DDoS
3: Intrusion detection, integrity checks, antivirus
4: Chroot, chrooting, jailing, comparimization
5: Forensics, recovery, undelete
6. Securing networked services

Some texts contain step by step directions for newbies, and some are directed at intermediate or expert users.
Please do not try to read everything in one go and post your questions in the Linux - Security forum. Comments/additions/corrections are welcome, just mail me.

Have fun!
Cheers, unSpawn

A note for copying. While this information is free, there are restrictions for copying. I collected and posted these resources here for the use of the larger Linux Community. This means you are free to copy this information, but you will give credit where credit is due and reference back adding this page as the original URI.
Don't pass it off as your own. All articles are available under the terms of a Creative Commons license.

WARNING: HTML lintcheck
Link validity isn't guaranteed and checking should have been done aeons ago.
If you find errors I would appreciate an email with a corrected link. TIA

Last edited by unSpawn; 02-25-2006 at 01:56 AM. Reason: // 2006/02/25 tt sync
Click here to see the post LQ members have rated as the most helpful post in this thread.
Old 02-13-2003, 04:01 PM   #2
Registered: May 2001
Posts: 28,886
Blog Entries: 55

Original Poster
Rep: Reputation: 3356Reputation: 3356Reputation: 3356Reputation: 3356Reputation: 3356Reputation: 3356Reputation: 3356Reputation: 3356Reputation: 3356Reputation: 3356Reputation: 3356
Basics etc

Post 1
Basics, important sites, HOWTO's, handbooks, hardening, tips
Advisories, alerts, bulletins, disclosure, mailinglists, mailing archives, knowledge bases, other sites
Hardening, distro-specific
Log analysis tools, resources
Daemons, device or application specific
More Brainfood, sites, books

Basics, important sites, HOWTO's, handbooks, hardening, tips

AusCERT UNIX and Linux Security Checklist v3.0:
UNIX Security Checklist v2.0:
SANS, The Twenty Most Critical Internet Security Vulnerabilities:
SANS SCORE Checklists for W32/Solaris/Cisco IOS/Mac OS/etc etc:
SANS, Reading room, Linux Issues:

CERT, Security improvements:
CERT, Tech Tips:
Linux Administrator's Security Guide (LASG):
Linux Security Administrator's Guide (SAG, old):
The Linux Network Administrator's Guide (NAG):
Securing & Optimizing Linux: The Ultimate Solution (PDF):
Securing Optimizing Linux RH Edition (older):
Linux Security HOWTO:
Linux Security Quick Reference Guide (PDF):
Security Quick-Start HOWTO for Linux,:
Security links at Linuxguru's:
TLPD Networking security HOWTO's:

Compromise, breach of security, detection
Intruder Detection Checklist (CERT): now archived at
Detecting and Removing Malicious Code (SF):
Steps for Recovering from a UNIX or NT System Compromise:
Formatting and Reinstalling after a Security Incident (SF):
How to Report Internet-Related Crime ( CCIPS):
Related, old(er) articles/docs:
Intruder Discovery/Tracking and Compromise Analysis:
Intrusion Detection Primer:
Through the Looking Glass: Finding Evidence of Your Cracker (LG):
Recognizing and Recovering from Rootkit Attacks:
See also post #5 under Forensics docs

Advisories, alerts, bulletins, disclosure, mailinglists, mailing archives, knowledge bases, other sites
Bugtraq (running):
or RSS:
or RSS (Advisories):
or RSS (News articles):
or RSS (Vulns):
Securitytracker (Advisories):

Neohapsis (mailinglists/archives):
theaimsgroup (mailinglists/archives):
Der Keiler (mailinglists/archives):

Linux Gazette:
Experts exchange:
The Linux Documentation Project:
Blacksheep (HOWTO's, whitepapers, etc):
E-secure-db Security Information database:
Linuxmag, Hardening Linux Systems:
Matt's Unix Security Page:
Jay Beale's docs (Bastille-linux/CIS):
The Unix Auditor's Practical Handbook:
Aging stuff from Phrack like "Unix System Security Issues":

Mailinglists distro specific:

Our own markus1982 on a roll! LQ HOWTO: securing debian: (search for



Conectiva Linux (subscribe for URL above URL; security-mailinglist Lingua Franca is Portugese, but on updates-mailinglist it's Engish. The last one always has the packages updates announced on security-mailinglist.

Slackware (subscribe for URL above)

# We need to incorporate more distro's here.

Hardening, distro specific
Debian/Mandrake/Red Hat: Bastille Linux:
Debian Security HOWTO:
Debian Security FAQ:
Mandrake: msec-*.rpm:
Slackware: Slackware Administrators Security tool kit:

Log analysis tools, resources
Auditd: Linux Audit:
Auditd: CAPP rules example:
Tools & Tips for auditing code:
Track unlink syscall (rm): TrackFS, libauditunlink, LAUS, LTT (Syscalltrack on 2.4)
# FWanalog (Summarizes IPF & IPtables firewall logs)
# FWlogsum (Summarizes Checkpoint FW1 logs)
# FWlogwatch (Summarizes firewall & IDS logs)
# KLogger (WinNT/Win2K keystroke logger)
# Linux Event Logger (For Enterprise-Class Systems):
# Lmon (PERL-based real time log monitoring solution)
# LogSentry (Monitors logs for security violations)
# Logsurfer (Monitors logs in realtime)
# PIdentd (Provides UserID with TCP connects)
# Swatch (Monitors syslog messages)
# Secure Remote Syslogger (Encrypted streaming syslog)
# SnortSnarf (HTMLized Snort Log Reviewer)
# Syslog-NG (Replacement for standard syslog facility)
# Syslog.Org (Vast info on syslogging)
# Throughput Monitor (An event counter per timeframe log analyzer): (check the library):
Counterpane, Log Analysis Resources:
EVlog, Linux Event Logging for Enterprise-class systems
Throughput Monitor
Need to add: Snare, LTK etc etc

Daemons, device or application specific
The Linux-PAM System Administrators Guide
Securing Xwindows:
How to Build, Install, Secure & Optimize Xinetd: #(link gone, see:
Installation of a secure webserver (SuSE): #(link gone, do a websearch for "suse_secure_webserver.txt")
Linksys security (LQ notes on):

Auditing tools at:

More Brainfood, sites, books
Daryl's TCP/IP primer:
Teach Yourself TCP IP in 14 Days (PDF): click on the link to download a 1.3 Meg PDF
Uri's TCP resource list:
Macmillan's "Maximum Security"
O'Reilly's TCP/IP Network Administration
* O'Reilly has a myriad of books some of which can also be found online, just search for "O'reilly and bookshelf", "o'reilly reference bookshelf" or "o'reilly cd bookshelf".

Last edited by unSpawn; 06-02-2009 at 07:38 AM. Reason: //tt sync 20090602
13 members found this post helpful.
Old 02-13-2003, 04:03 PM   #3
Registered: May 2001
Posts: 28,886
Blog Entries: 55

Original Poster
Rep: Reputation: 3356Reputation: 3356Reputation: 3356Reputation: 3356Reputation: 3356Reputation: 3356Reputation: 3356Reputation: 3356Reputation: 3356Reputation: 3356Reputation: 3356
Netfilter, firewall, Iptables etc

Post 2
Netfilter, firewall, Iptables, Ipchains, DoS, DDoS

*Please note the easiest way to troubleshoot Netfilter related problems is to add log (target) rules before any "decision" in a chain.
** Please note there's a LOT of firewall scripts on LQ: just search the Linux - Security and Linux - networking fora please.

LQ search, iptables+howto:
IPTables Tutorial: http://iptables-tutorial.frozentux.n...-tutorial.html
IPSysctl Tutorial: http://ipsysctl-tutorial.frozentux.n...-tutorial.html Packetfiltering HOWTO: Iptables tutorial:
Iptables Connection tracking:
Taking care of the New-not-SYN vulnerability:

TLDP Ipchains HOWTO: Ipchains HOWTO:

Web-browsers, mail clients, FTP clients, IM, P2P ports database for building your own rules:

Other resources/misc stuff
Basic introduction to building ipchains rules:
Explanation of the Ipchains logformat:
Ipchains log decoder:
Basics on firewalling:
CERT: Home Network Security:
Firewall FAQ:
Assigned ports > 1024:
Port designations:
Firewall Forensics FAQ (What am I seeing?):
Linux Firewall and Security Site:
Auditing Your Firewall Setup (old, still usefull), :
TLDP: Firewall Piercing mini-HOWTO:
Something called the "Home PC Firewall Guide":
Vendor/Ethernet MAC Address Lookup:
Netfilter Iptabes/Ipchains Log Format:
Dshield (find out if IP was marked as used in attacks):
Port search (Snort):
Neohapsis Port search:
P2P ports (IPMasq):
Is "Stealth" important?:
Infosyssec's Firewall Security and the Internet (badly updated site):

Webbased portscan services

DoS info
Hardening the TCP/IP stack to SYN attacks:
SANS, Help Defeat Denial of Service Attacks: Step-by-Step:
SANS, ICMP Attacks Illustrated:
CERT, Denial of Service Attacks:
NWC, Fireproofing Against DoS Attacks (forms of):

DDoS info
SANS, Consensus Roadmap for Defeating Distributed Denial of Service Attacks:
SANS, Spoofed IP Address Distributed Denial of Service Attacks: Defense-in-Depth:
SANS, Understanding DDOS Attack, Tools and Free Anti-tools with Recommendation:, Minimizing the Effects of DoS Attacks:
CISCO, Strategies to Protect Against Distributed Denial of Service (DDoS) Attacks:
Dave Dittrich's references:
Xinetd Sensors:
Xinetd FAQ:

Last edited by unSpawn; 11-02-2013 at 01:11 PM. Reason: //b0rken link
9 members found this post helpful.
Old 02-13-2003, 04:05 PM   #4
Registered: May 2001
Posts: 28,886
Blog Entries: 55

Original Poster
Rep: Reputation: 3356Reputation: 3356Reputation: 3356Reputation: 3356Reputation: 3356Reputation: 3356Reputation: 3356Reputation: 3356Reputation: 3356Reputation: 3356Reputation: 3356
Intrusion detection etc

Post 3
Intrusion detection, integrity checks: IDS, NIDS, HIDS, Antivirus, software.

Note: vulnerability checking: CIS, SATAN, COPS, Tiger

FAQ: Network Intrusion Detection Systems:
Sniffin' the Ether v2.0:
Lotek sniffing docs:
Defeating Sniffers and Intrusion Detection Systems, Phrack,

The IDS acronym game:

IDS: Intrusion Detection System refers to an application able to examine traffic for attributes and properties that mark "benign", suspicious, restricted, forbidden or outright hostile activities.

NIDS: Network IDS refers to Intrusion Detection, like running "sensors" on various sentry or sniffer hosts while logging and/or logprocessing and alerting is done on a central host (many-to-one topology).
NIDS examples are:
OSSIM (Snort+Acid+mrtg+NTOP+OpenNMS+nmap+nessus+rrdtool):
Panoptis (DoS, DDoS only):
Some commercial/non OSS examples: Demarc PureSecure, Cisco Secure IDS (NetRanger), ISS Real Secure, Axent Net Prowler, Recourse ManHunt, NFR Network Flight Recorder, NAI CyberCop Network, Enterasys Dragon and Okena Stormfront/Stormwatch.
Snort also is available commercially these days.

HIDS: Host-based IDS. The HIDS acronym itself is subject to flamewars.
IDS examples are Snort, Shoki, Prelude, Defenseworx, Pakemon, Firestorm and Panoptis (DoS, DDoS only).

IPS: Intrusion Protection System. Passive or active (learning, like the heuristics stuff?) enforcement of rules at the application, system or access level. I suppose we're looking at stuff like Grsecurity, Solar Designer's Open Wall, LIDS, LOMAC, RSBAC, Linux trustees, Linux Extended Attributes, LIDS or Systrace here.
Commercial/non OSS examples: Entercept, ISS RealSecure, Axent Intruder Alert Manager, Enterasys' Dragon, Tripwire, Okena and CA's eTrust.

Intrusion Detection Systems: An Introduction:
Intrusion Detection FAQ (SANS, handling ID in general):
Basic File Integrity Checking (with Aide): (IDS, NIDS, File Integrity Checkers)

Snort basics:
Using Snort as an IDS and Network Monitor in Linux (SANS, PDF file):
Snort: IDS Installation with Mandrake 8.2, Snort, Webmin, Roxen Webserver, ACID, MySQL:
ArachNIDS (Snort/Dragon/Defenseworx/Pakemon/Shoki rule, research and info library):
Intrusion Detection and Network Auditing on the Internet:
Snort Stealth Sniffer: Paranoid Penguin: Stealthful Sniffing, Intrusion Detection and Logging:

Dropping Packets with Snort:
Why not to use Snort's "flexresp":
Guardian: see the Snort tarball, in the contrib dir.

Snort GUI's, management, log reporting and analysis:
Snort Unified Logging: Barnyard: (Sourceforge)
Snort Unified Logging: Logtopcap
Snort Unified Logging: Mudpit
Analysis Console for Intrusion Databases (ACID):
HOWTO Build Snort with ACID:
SPADE, Snortsnarf:
Enabling Automated Detection of Security Events that affect Multiple Administrative Domains:
Demarc (commercial):
Oinkmaster (rulemanagement):
Snort alert mailer (C or .pe?r?l?):
Pig Sentry:
IDS Policy Manager Version (W32):
Snort_stat: /var/log/snort/alert | /usr/lib/sendmail <human@someh.ost>
Swatch: ./swatch -c /root/.swatchrc --input-record-separator="\n\n" --read-pipe="tail -f /var/log/snort/alert" --daemon
Swatch + Hogtail.

Snort vs Abacus Portsentry:
Snort and PortSentry compared:

Comparison of IDSs ( NFR NID, Snort, INBOUNDS, SHADOW, Dragon, Tripwire):

Snort help, mailinglist (archives), honeypots:
Snort: Database support FAQ:
Snort mailinglists, Aims:
Snort IDS forum at
Baby steps with a honeypot:
Honeypot & Intrusion Detection Resources:
The TCP Flags Playground (Mailinglist, Neohapsis):

Snort + 802.11 aka Wireless:

Sniffing (network wiretap, sniffer) FAQ:
Apps, network monitoring (index):

An Analysis of a Compromised Honeypot (Snort+Ethereal):
To add: Firestorm NIDS, Barnyard, Mudpit, Snort GUI's, add-ons etc etc.

Snort on two interfaces, solution one: "-i bond0".
Valid-for: running one Snort instance, multiple promiscuous mode interfaces except the mgmnt one.
Caveat: none
See-also: Documentation/networking/bonding.txt
Do once: "echo alias bond0 bonding >>/etc/modules.conf"
At boot: "ifconfig bond0 up; ifenslave bond0 eth0; ifenslave bond0 eth1"
At boot: start Snort with interface arg "-i bond0"

Snort on two interfaces, solution two: "-i any"
Valid-for: running one Snort instance, all interfaces.
Caveat: you loose promiscuous mode.
At boot: start Snort with interface arg "-i any" and a BPF filter to stop it from logging the loopback device.

File Integrity Detection Systems
Checking a filesystem's contents against one or more checksums to determine if a file (remember anything essentially is a file on a Linux FS) has been changed.
Examples are:
Aide: (for remote mgmnt see also ICU or RFC which handles Aide, Integrit and Afick)
Samhain: (for remote mgmnt see docs)
Tripwire (for remote mgmnt see FICC:
Chkrootkit (not only Linux):
Rootkit Hunter (not only Linux):

Commercial/non OSS examples: Versioner, GFI LANguard System Integrity Monitor, Ionx's Data Sentinel, Tripwire for Servers and Pedestal Software Intact.
File Integrity (SecurityFocus, tools list):

Viruses on Linux/GNU, Antivirus software

Sendmail, Tcpdump, OpenSSH, TCP Wrappers, Aide and some other projects have suffered from people succeeding to inject malicious code, and of those only Sendmail and OpenSSH where at main servers, the rest where mirrors AFAIK. Even though all the apps mentioned are safe to use, and the differences where noted soon, the real problem is you I. have to have the knowledge to read code, and II. the discipline to read the code each time and question any diffs or III. have minimal "protection" in place to cope with like rogue compiled apps "phoning home". Which in essence means to end users any SW provided w/o means to verify integrity of the code and the package should be treated with care, instead of accepting it w/o questioning.

As for the "virus" thingie I wish we, as a Linux community, try to "convert" people away from the typical troubles of Pitiful Operating Systems (abbrev.: POS, aka the MICROS~1 Game Platform) and direct them towards what's important to know wrt Linux: user/filesystem permissions, b0rken/suid/sgid software, worms, trojans and rootkits.

Basic measures should be:
- Using (demanding) source verification tru GPG or minimally md5sums,
- Watch system integrity (Aide, Samhain, Tripwire or any package mgr that can do verification: save those databases off-site, also see Tiger, Chkrootkit),
- Harden your systems by not installing SW you don't need *now*, denying access where not needed and using tools like Bastille-linux, tips from Astaro,
- Patch kernel to protect looking at/writing to crucial /proc and /dev entries and/or use ACL's (see Silvio Cesare's site, Grsecurity, LIDS),
- Watch general/distro security bulletins and don't delay taking action (Slapper, Li0n etc),
- Keep an eye on outgoing traffic (egress logging and filtering),
- Don't compile apps as root but as a non-privileged user,
- Inspect the code if you can,
- Don't use Linux warez,
But most of all: use common sense.

*If you're still not satisfied you've covered it all you could arm yourself with knowledge on forensics stuff like UML, chrooting, disassembly and honeypots.

If you want to find Antivirus software, Google the net for Central Command, Sophos, Mcafee, Kaspersky, H+BEDV, Trend Micro, Frisk, RAV, Clam, Amavis, Spam Assassin, Renattach, Ripmime, Milter or Inflex.
- AV SW is as good as it's signatures/heuristics. Some vendors don't update their Linux sig db's very well, or field SW with lacking capabilities. I've tested some (admittedly a long time ago) on my virus/trojan/LRK/malware libs. Bad (IMHO): Frisk's F-Prot (sigs), Clam (sigs), H+BEDV (libc version). Good (IMNSHO): Mcafee's uvscan (best) and RAV (2nd). Please do test yourself.
- AFAIK only KAV (Kaspersky) has a realtime scanner daemon. I'm in limbo about it's compatibility with recent kernels tho.

Links to check out:
LAVP/Mini-FAQ Linux/Unix AV SW,
NIST (list of AV vendors),

Last edited by unSpawn; 10-04-2006 at 03:52 PM.
6 members found this post helpful.
Old 02-13-2003, 04:12 PM   #5
Registered: May 2001
Posts: 28,886
Blog Entries: 55

Original Poster
Rep: Reputation: 3356Reputation: 3356Reputation: 3356Reputation: 3356Reputation: 3356Reputation: 3356Reputation: 3356Reputation: 3356Reputation: 3356Reputation: 3356Reputation: 3356
Chrooting etc

Post 4
Chroot, chrooting, jailing, comparimization

Chroot Jails Made Easy with the Jail Chroot Project:
Chrooting MySQL HOWTO (LQ):
Apache, PHP, MySQL:

OpenSSH for chrooted sessions on Linux:
OpenSSH, Scponly:
Using scponly for secure file transfers:
OpenSSH, Rssh:
OpenSSH Sftp logging patch, contact Mike Martinez:

How to chroot an Apache tree with Linux and Solaris:
An Overview of 'chroot jailing' Services in Linux:
How to break out of a chroot() jail:
Breaking out of a restricted shell:, down at "Breaking Out of Various Restrictions"
Tech-Babble: Virtual Server Myth:
0x05: Why chroot(2) Sucks:
Chuvakin A.,:
Chrooting daemons and system processes HOW-TO:

Other SW/HOWTO's unsorted for BIND

Last edited by unSpawn; 02-24-2004 at 07:33 PM.
6 members found this post helpful.
Old 02-13-2003, 04:14 PM   #6
Registered: May 2001
Posts: 28,886
Blog Entries: 55

Original Poster
Rep: Reputation: 3356Reputation: 3356Reputation: 3356Reputation: 3356Reputation: 3356Reputation: 3356Reputation: 3356Reputation: 3356Reputation: 3356Reputation: 3356Reputation: 3356
Forensics, recovery, undelete

Post 5
Forensics, recovery, undelete

Forensics HOWTO's, docs
Steps for Recovering from a UNIX or NT System Compromise:
Open Web Application Security Project (OWASP):
Open Source Computer Forensics Manual:
OSSTM: Institute for Security and Open Methodologies (formerly
Forensics Basic Steps: or
Dd and netcat cloning disks:
Security Applications of Bootable Linux CD-ROMs:
Honeypot project (Hone your skills with the SOM):
RH8.0: Chapter 11. Incident Response (Red Hat Linux Security Guide):
Forensics and Incident Response Resources:
Forensics presentation by Weld Pond and Tan:
Law Enforcement and Forensics Links.:
Forensics commercial svc's:

Forensics CDR's
FIRE (formerly Biatchux +TCT):
The Penguin Sleuth Kit (Knoppix-based +TCT + Sleuthkit):

Forensics tools
OSSTM Tools listing:
The Coroners Toolkit (TCT): or
tomsrtbt (1 floppy distro):
Trinux, (Pentest/sniff/scan/recovery/IDS/forensics CD):
Snarl (Forensics CD based on FreeBSD):
Freeware Forensics Tools for Unix:
The @stake Sleuth Kit (TASK):
Tools used by CSIRTs to Collect Incident Data/Evidence, Investigate and Track Incidents (list):
Freeware Forensics Tools (reflist, Linux w32).:
TUCOFS - The Ultimate Collection of Forensic Software, :
Response kits (precompiled static binaries for Linux, Slowaris and wintendo):
Precompiled static binaries for Linux (iso):
Forensic Acquisition Utilities for w32:
CREED (Cisco Router Evidence Extraction Disk),:
...else check, Packetstorm,, whatever.

Undelete HOWTO's
Recovering a Lost Partition Table:
Linux Partition HOWTO:
How to recover lost partitions:
Linux Ext2fs Undeletion mini-HOWTO:
Linux Partition Rescue mini-HOWTO:
File Recovery.v.0.81 (using Midnight Commander):

Rescue tools for partition table/ext2fs
Recover (app + info):
Also see mc (the Midnight Commander)
TCT (above).

Rescue tools from dd image

Rescue tools for FAT/VFAT/FAT32 from Linux

Partition imaging
: http://www.partimage.orgPartimage.
* For more rescue tools check, or other depots for a /Linux/system/recovery/ dir.

II. Runefs: The first inode that can allocate block resources on a ext2 file system is in fact the bad blocks inode (inode 1) -- *not* the root inode (inode 2). Because of this mis-implementation of the ext2fs it is possible to store data on blocks allocated to the bad blocks inode and have it hidden from an analyst using TCT or TASK. To illustrate the severity of this attack the following examples demonstrate using the accompanying runefs toolkit to: create hidden storage space; copy data to and from this area, and show how this area remains secure from a forensic analyst.:

//If you've read this far and you aren't a professional system administrator: congrats. LQ doesn't ask you nothing in return but to spread around whatever good security practices you know. If you want to add a section or a link: please email me. License information: see top of thread.

Last edited by unSpawn; 02-24-2004 at 07:37 PM.
8 members found this post helpful.
Old 02-25-2006, 02:04 AM   #7
Registered: May 2001
Posts: 28,886
Blog Entries: 55

Original Poster
Rep: Reputation: 3356Reputation: 3356Reputation: 3356Reputation: 3356Reputation: 3356Reputation: 3356Reputation: 3356Reputation: 3356Reputation: 3356Reputation: 3356Reputation: 3356
Securing networked services

Post 6
Securing networked services

Web Security Appliance With Apache and mod_security (SF):
Securing Apache Step-by-Step:
Securing apache2:

Apache suEXEC Support:
HOWTO Install PHP with SuExec:
HOWTO Install PHP as CGI with Apache's suEXEC Feature:
How to set up suexec to work with virtual hosts and PHP (+PHP +public_html patch):

Apache modules
Apache mod_security guide:
Secure Your Apache With mod_security:
Apache mod_ssl:
mod_security rulesets:
mod_security rule generator:

Securing MySQL Step-byStep:
Secure MySQL Database Design:
Database Security Explained:
SQL injection attack mitigation: SafeSQL:,
Detect SQL injection attacks: class_sql_inject:

The Problem With PHP Application Security:
PHP and the OWASP Top Ten Security Vulnerabilities:
Top 7 PHP Security Blunders:
PHP Security Guide: (PHP Security Library: Security Guide considered harmful:
PHP: Preventing register_global problems:
Securing PHP Step-by-Step:
PHP Security:
Security of PHP: (PHP Foundations:
Auditing PHP, Part 1: Understanding register_globals:
Hardened PHP:
( seems outdated)

Checking PHP
CastleCops Analyzer (Nuke only?):

Exploiting Common Vulnerabilities in PHP Applications

Security network testing
Metasploit Framework:

Application security testing
Open Web Application Security Project (OWASP):

OAT (Oracle Auditing Tools):

SMBAudit (auditing):

Secure BIND Template Version 5.1 05 JAN 2006:
Securing an Internet Name Server:
DNS Security and Vulnerabilities:

General remarks:
Do not allow root account logins with ssh
Do use public key authentication
Restrict access if possible sshd_config: AllowGroups,AllowUsers and/or TCP wrappers, firewall, Xinetd entry, PAM ACL.
Stop bruteforcing (in no particular order):
Samhain: Defending against brute force ssh attacks:

Last edited by win32sux; 08-21-2009 at 06:48 AM. Reason: Added link to previously-stickied PHP security LQ thread.
10 members found this post helpful.

Closed Thread

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
shell references nariman Linux - Newbie 3 02-25-2006 06:36 AM
??Good C References Please?? InvisibleSniper Programming 9 10-28-2005 02:45 PM
references jenny_psion Programming 0 08-12-2003 04:06 AM
re: FAQ: Security references german Linux - Security 1 07-14-2003 05:54 AM
references to other other sites pbharris LQ Suggestions & Feedback 10 04-10-2002 11:20 AM

All times are GMT -5. The time now is 05:32 AM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration