Linux System Administration Recipes A Problem-Solution Approach

More documents

Recommendations

Info

CHAPTER 6 ■ SECURING YOUR SYSTEMS01 iptables -A SSH -j LOG --log-prefix "ssh:"02 iptables -A SSH -m limit --limit 3/min --limit-burst 3 -j ACCEPT03 iptables -P SSH DROPLine 01 logs all connections (see line 05 in the first setup). Line 02 does the limiting work. The limitis set at three connections per minute, but this is an average. limit-burst sets how often the average ischecked. So here, the rule will be checked after three connections. If those three connections havehappened within a minute, the limiting is triggered; no further packets will be accepted until a fullminute has passed (whereupon we’re back below the three per minute rate). If you set --limit-burst as6, you could get six connections through as fast as you like, but after that you would have to wait untiltwo minutes had passed since the first connection to have another packet accepted.Line 03 sets the chain policy to DROP; so, all other packets are dropped.Finally, we have the issue of when to trigger this. We want to replace line 06 in the first listing, whichis also rule 6 in the INPUT chain (execute iptables -L –linenumbers -n to check this). Use this commandto replace (-R) rule 6 with this definition:iptables -R INPUT 6 -d 192.168.100.25 -p tcp -m tcp --dport 22 -j SSHThis passes all SSH connections (in other words, TCP connections coming in on the SSH port, port21) to the SSH chain.You can also get rid of rule 5, since the logging is now done in the SSH chain:iptables -D INPUT 5■ Note Remember that after this rule is deleted, the numbering of the rules in the chain will change! It’s alwayswise to use iptables -L --linenumbers to check rule numbers before you make changes.Now, an SSH packet for this machine will be passed to the SSH chain and rate limited.6-14. Monitoring for Break-ins with chkrootkitchkrootkit enables you to have a set of important files monitored for signs of an attacker breaking in, forrootkits, and for worms and other similar nasties. You can set it up to send you information on a regularbasis.It should be available as a package for most distros. On Debian/Ubuntu, install it like this:sudo apt-get install chkrootkitAlternatively, install from source from http://www.chkrootkit.org/.You can run it manually with /usr/sbin/chkrootkit. You should see a list of files being checked and(ideally!) all having “not infected” after their names. You’ll also see the program searching for variousspecific worms and rootkits and for suspicious files generally. If anything has been found, you’ll see thestring INFECTED.152Download at WoweBook.Com
CHAPTER 6 ■ SECURING YOUR SYSTEMS■ Note It does have a tendency to generate false positives, such as dot files installed in unusual places or serversrunning on nonstandard ports. Line 03 in the following setup means that false positives will occur only once,however, rather than repeatedly showing up.What you want, though, is to have this run automatically on a daily basis. If you’ve installed theDebian/Ubuntu package, this includes the file /etc/cron.daily/chkrootkit that will do this for you,which looks like this:#!/bin/sh -eCHKROOTKIT=/usr/sbin/chkrootkitCF=/etc/chkrootkit.confLOG_DIR=/var/cache/chkrootkitif [ ! -x $CHKROOTKIT ]; thenexit 0fiif [ -f $CF ]; then. $CFfiif [ "$RUN_DAILY" = "true" ]; thenif [ "$DIFF_MODE" = "true" ]; then$CHKROOTKIT $RUN_DAILY_OPTS > $LOG_DIR/log.new 2>&1if [ ! -f $LOG_DIR/log.old ] \|| ! diff -q $LOG_DIR/log.old $LOG_DIR/log.new > /dev/null 2>&1; thencat $LOG_DIR/log.newfimv $LOG_DIR/log.new $LOG_DIR/log.oldelse$CHKROOTKIT $RUN_DAILY_OPTSfifiTo set chkrootkit options, you can set environment variables in /etc/chkrootkit.conf. This is agood default setup:01 RUN_DAILY="true"02 RUN_DAILY_OPTS="-q -n"03 DIFF_MODE="true"Line 01 sets daily running (unsurprisingly!). -q runs quietly, and -n skips NFS-mounted directories.Line 03 means that output will be generated only if it differs from the previous day’s output. In otherwords, you will be warned only once! This means that if you have regular false positives, you won’talways receive an e-mail; however, it also means that if you miss the first warning (maybe in a153Download at WoweBook.Com
Page 2:
Download at WoweBook.Com
Page 5 and 6:
Download at WoweBook.Comiii
Page 7 and 8:
Contents■About the Author .......
Page 9 and 10:
■ CONTENTS3-7. Writing a Nagios P
Page 11 and 12:
■ CONTENTS■Chapter 8: Using the
Page 13 and 14:
■ CONTENTSAbout the Author■Juli
Page 15 and 16:
■ CONTENTSAcknowledgmentsMany tha
Page 17 and 18:
■ CONTENTSIntroductionThis book i
Page 19 and 20:
■ INTRODUCTIONDownloading the Cod
Page 21 and 22:
C H A P T E R 1■ ■ ■Saving Yo
Page 23 and 24:
CHAPTER 1 ■ SAVING YOURSELF EFFOR
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
C H A P T E R 2■ ■ ■Centraliz
Page 43 and 44:
CHAPTER 2 ■ CENTRALIZING YOUR NET
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
C H A P T E R 3■ ■ ■Monitorin
Page 85 and 86:
CHAPTER 3 ■ MONITORING AND UPDATI
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
C H A P T E R 4■ ■ ■Taking Ba
Page 117 and 118:
CHAPTER 4 ■ TAKING BACKUPS AND MA
Page 119 and 120:
CHAPTER 4 ■ TAKING BACKUPS AND MA
Page 121 and 122: CHAPTER 4 ■ TAKING BACKUPS AND MA
Page 139 and 140: C H A P T E R 5■ ■ ■Working w
Page 141 and 142: CHAPTER 5 ■ WORKING WITH FILESYST
Page 155 and 156: C H A P T E R 6■ ■ ■Securing
Page 157 and 158: CHAPTER 6 ■ SECURING YOUR SYSTEMS
Page 171: CHAPTER 6 ■ SECURING YOUR SYSTEMS
Page 179 and 180: CHAPTER 7 ■ WORKING WITH APACHEOn
Page 181 and 182: CHAPTER 7 ■ WORKING WITH APACHEdi
Page 183 and 184: CHAPTER 7 ■ WORKING WITH APACHE4.
Page 185 and 186: CHAPTER 7 ■ WORKING WITH APACHE
Page 187 and 188: CHAPTER 7 ■ WORKING WITH APACHEAl
Page 189 and 190: CHAPTER 7 ■ WORKING WITH APACHE
Page 191 and 192: C H A P T E R 8■ ■ ■Making Be
Page 193 and 194: CHAPTER 8 ■ USING THE COMMAND LIN
Page 207 and 208: CHAPTER 9 ■ WORKING WITH TEXT IN
Page 223 and 224:
C H A P T E R 10■ ■ ■Things G
Page 225 and 226:
CHAPTER 10 ■ THINGS GO IN, THINGS
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
C H A P T E R 11■ ■ ■Tracking
Page 235 and 236:
CHAPTER 11 ■ TRACKING DOWN BUGSTh
Page 237 and 238:
CHAPTER 11 ■ TRACKING DOWN BUGS01
Page 239 and 240:
CHAPTER 11 ■ TRACKING DOWN BUGS
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
CHAPTER 11 ■ TRACKING DOWN BUGSTh
Page 247 and 248:
CHAPTER 11 ■ TRACKING DOWN BUGSAn
Page 249 and 250:
CHAPTER 11 ■ TRACKING DOWN BUGS#
Page 251 and 252:
C H A P T E R 12■ ■ ■Managing
Page 253 and 254:
CHAPTER 12 ■ MANAGING TIME AND PE
Page 255 and 256:
Page 257 and 258:
Page 259 and 260:
Page 261 and 262:
Page 263 and 264:
Page 265 and 266:
Page 267 and 268:
APPENDIX■ ■ ■Perl TipsSee rec
Page 269 and 270:
APPENDIX ■ PERL TIPS• Date::Par
Page 271 and 272:
APPENDIX ■ PERL TIPSPerl Syntax N
Page 273 and 274:
■ ■ ■Index■Symbols$CDPATH,
Page 275 and 276:
■ INDEXenscript option (printing)
Page 277 and 278:
■ INDEX■NNagiosadding hosts to,
Page 279 and 280:
■ INDEXsyslogcentralized logging
Page 281 and 282:
Download at WoweBook.Com
show all

Linux System Administration Recipes A Problem-Solution Approach

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?