Some Good Tips to Secure Linux
Darknet spilled these bits on April 15th 2006 @ 9:09 am

I came across this while browsing, has some pretty solid stuff, goes deeper than most basic Linux security guides.

It has some good sections like this on protection against fork bombs:

Fork bombs are programs that keep creating child processes until system resources are all used, they actually aren’t remote exploits because they require a local user to execute the bomb, however, users may be tricked into running a fork bomb, for example the following example may look innocent, but running it on an unprotected system may take the whole system down:

:( ){ : |:& }; :

WARNING: do NOT run the above code on an unprotected system!

The above shell script will actually keep forking at an exponential rate until system resources are exhausted.

To protect a system against such attacks, there is a file for limiting the number of processes for each user, it is /etc/security/limits.conf, add the following two lines to it:
@users soft nproc 100
@users hard nproc 150

The lines prevent anyone in the users group from having more than 150 processes, and issue a warning at 100 processes.

Your system may not have a users group, so you may need to edit the lines to suit your needs.

There are some other things you can do like using a file integrity checker, installing a log checker or centralising logs with something like syslog-ng, scanning for SU files on a regular basis, setup alerts if a new user is added and so on, but this gives you a start.

It has some security tips for OpenSSH, Samba and MySQL too.

I recommend taking a look anyway!

Tips to Secure Linux Workstation

Tags:  ,  ,  ,  ,  ,  ,  

rss Subscribe to Darknet RSS Feed rss

| 6,631 views |

rss 3 comments
  1. zupakomputer
    March 7th, 2008 | 9:22 pm

    That, is a splendid website there. A wealth of useful information & links.

    Cheers!

  2. Pantagruel
    March 8th, 2008 | 12:19 pm

    @zupakomputer

    Indeed a nice set of tips.
    Some a bit ’security through obscurity’ inspired, port obfuscation (like mentioned for SSH) doesn’t do much for the hardened ssh hackers/crackers.

  3. zupakomputer
    March 8th, 2008 | 3:27 pm

    Yeah well they acknowledged that in the blog - it’s meant more to avoid automatic scanners and the kinds of people that are just using malware applications but don’t actually know how they work.

comment on this article

Sitemap - ShaolinTiger - DigiSniper - Digital Photography
Shutter Asia Photography Forum - We Ate This