Linux System Administration Recipes A Problem-Solution Approach

More documents

Recommendations

Info

CHAPTER 7 ■ WORKING WITH APACHEaddresses is allowed (line 06). Note that it works rather like a regular expression, in that it’ll match onlywhatever is provided. So, this line allows any IP address of the form 192.168.*.*. <strong>Problem</strong> solved.But maybe you’d like your local users to be able to access these pages from home as well. In thiscase, you can add an alternative way of accessing these pages by setting up a special local user. The.htaccess file should look like this:AuthUserFile /etc/apache2/.htpasswdAuthName Local PagesAuthType BasicSatisfy Anyorder deny,allowdeny from allallow from 192.168.require user localNote the Satisfy Any directive; this means you can either be in the correct IP range (you can alsospecify by domain) or have the correct username and password. The default is Satisfy All, which wouldmean that you’d need both to be in the correct domain and to have the correct credentials.For setting the username up, the key point is the AuthUserFile directive, which sets up a file thatApache will check for the password of your user local as set up in the LIMIT section.The next step is to create the htpasswd file, using this command:htpasswd -c /etc/apache2/.htpasswd local■ Note The -c switch is used only to create the file. If you go to add another user, just use htpasswd/etc/apache2/.htpasswd otheruser.You’ll be challenged for the password for the user, which will be encrypted and put in the file. Makesure that only the Apache2 user can read this file:chown www-data /etc/apache2/.htpasswd; chmod og-r /etc/apache2/.htpasswd■ Note The .htpasswd file can live wherever you like, but for security reasons it should not live anywhere in yourweb data directories. Keep it instead with your Apache2 config. In this case, it doesn’t need to be a dot file(.htpasswd) because it won’t be visible to the average user anyway; you can just call it htpasswd.Now try loading a page in that directory from an IP address outside your local subnet; you should bechallenged for the username and password. Enter them, and you’re allowed in. Pass this username andpassword on to the users you want to be able to access your machine.168Download at WoweBook.Com
CHAPTER 7 ■ WORKING WITH APACHE■ Note This kind of single username/password access, where everyone uses the same authorization, is not verysecure! Be careful how sensitive the information is that you protect in this way. However, it’s useful if yourintention is simply to keep the information off the public Internet at large.7-6. Securing Your Web Site: Apache with KerberosYou may have parts of your web site that you want only your users to be able to access or a section thatyou want people to log into as themselves. If you’re running a ticketing system or anything of that sort,then this is particularly useful. For some of these options, htaccess is useful (see recipe 7-5), but if youwant individual users to log in as themselves, then tying authentication in with Kerberos is by far thebest bet. This means that you don’t have to repeat your username/password setup; you can just usewhat you already have established.■ Note This does assume that you already have Kerberos set up! See Chapter 2. Alternatively, you can use themod_authnz_ldap module (a2enmod authnz_ldap in Debian), which works with LDAP auth and with ActiveDirectory.The module you want is mod_auth_kerb, which is available from http://modauthkerb.sourceforge.net/ or in Debian/Ubuntu as the libapache2-mod-auth-kerb package.To install it, add this line to your Apache config file (or for Debian/Ubuntu, run a2enmodmod_auth_kerb):LoadModule auth_kerb_module /usr/lib/apache2/modules/mod_auth_kerb.soYou also need to set up a keytab for Apache to use. Run kadmin -p krbadm from your Apache server,and then execute these commands:> addprinc --randkey HTTP/webserver.example.com@EXAMPLE.COM> ktadd -k /etc/apache2/apache2.keytab HTTP/webserver.example.com@EXAMPLE.COMAfter this, set the correct permissions for the keytab; it should be readable only by the Apache2process:chown www-data /etc/apache2/apache2.keytabchmod og-r /etc/apache2/apache2.keytab169Download 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:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138: 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 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: CHAPTER 7 ■ WORKING WITH APACHEAl
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 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

Create successful ePaper yourself

Delete template?

Save as template?