Linux System Administration Recipes A Problem-Solution Approach

More documents

Recommendations

Info

CHAPTER 2 ■ CENTRALIZING YOUR NETWORK: KERBEROS, LDAP, AND NFSThe -nodes switch is important in order to create an unencrypted certificate sothat it will work with LDAP. Again, when asked for the CN, it needs to be theFQDN of your server. This time it will be the LDAP server (here ldapserver.example.com).If you’re using an external CA, leave out the -x509 option.3. Sign the certificate:cd /etc/ssl/usr/lib/ssl/misc/CA.sh –signcertAgain, do not use a challenge password. The new certificate will be in newcert.pem. (Note: this script looks for the file newreq.pem and signs that; if you haveused another file in the certificate creation, you will need to rename or copy it.)Remember where these files are—you’ll need to move them into the LDAP directory in the nextrecipe.2-3b. LDAP ServerFor Debian/Ubuntu, run this:sudo apt-get install libldap2 slapd ldap-utils libdb3-dev libdb3slapd is the LDAP server; libdb3-dev and libdb3 provide the BerkeleyDB database back end. Youcan use other databases, but BerkeleyDB is straightforward to deal with and is strongly recommended bythe OpenLDAP team. Set the admin password when asked during dpkg-configure.To use SSL (as per the certificate generated earlier), you need to put the certificates generated earlierin the correct places:mv /etc/ssl/newcert.pem /etc/ldap/servercrt.pemmv /etc/ssl/newreq.pem /etc/ldap/serverkey.pemmv /etc/ssl/demoCA/cacert.pem /etc/ldap/cacert.pemchmod go-r /etc/ldap/serverkey.pemchown openldap /etc/ldap/serverkey.pemchmod a+r /etc/ldap/servercrt.pemEdit /etc/default/slapd to include these lines (this provides LDAP both using TLS over port 389 andusing LDAPS on port 636):SLAPD_SERVICES="ldap:/// ldaps:///"SLAPD_OPTIONS="4"As discussed at the start of this chapter, using LDAP with Kerberos provides more secure passwordmanagement. To use LDAP with Kerberos, you need to get a copy of krb5-kdc.schema (available fromhttp://www.stanford.edu/services/directory/openldap/configuration/krb5-kdc.schema or from the/usr/share/doc/krb5-kdc-ldap/kerberos.schema.gz file included in the krb5-kdc-ldap package). Thenput it in the /etc/ldap/schema/ directory.30Download at WoweBook.Com
CHAPTER 2 ■ CENTRALIZING YOUR NETWORK: KERBEROS, LDAP, AND NFScd /etc/ldap/schema/wget http://www.stanford.edu/services/directory/openldap/configuration/krb5-kdc.schemaEdit /etc/ldap/slapd.conf. This is a long file, so I’ve included just the changes or additions youneed to make here:includeinclude/etc/ldap/schema/krb5-kdc.schema/etc/ldap/schema/openldap.schema# ... other things that can stay as provided by default...TLSCACertificateFileTLSCertificateFileTLSCertificateKeyFile/etc/ldap/cacert.pem/etc/ldap/servercrt.pem/etc/ldap/serverkey.pem# ... other things that can stay as provided by default...# this section rewrites principals as needed for Kerberos authenticationauthz-policy fromauthz-regexpuid=(.*),cn=example.com,cn=GSSAPI,cn=authuid=$1,ou=people,dc=example,dc=comsasl-realm EXAMPLE.COMsasl-host ldapserver.example.com# ... rest of file ...The authz section is important for setting up LDAP with Kerberos. The authz-policy line allows auser to authorize as someone else, if this is permitted in the second user’s LDAP entry. The authz-regexpline takes a Kerberos authorization request and translates it into an LDAP user identifier. $1 in thesecond line refers to the (.*) in the first line, which corresponds to the whole of the uid field in theKerberos auth.So, the Kerberos authorization for user jkemp would be as follows:uid=jkemp,cn=example.com,cn=GSSAPI,cn=authand would be converted to this:uid=jkemp,ou=people,dc=example,dc=comThe SASL information is used to complete the LDAP lookup information when using SASL.The next step is to edit your permissions, which are also set in /etc/ldap/slapd.conf. Either findand edit as appropriate the existing access lines in your config (Debian/Ubuntu includes some basicsetup) or add these lines in the main Specific Directives for Database section of the config file. Theexample here is a basic functional setup, in which the LDAP admin user has full write access andeveryone has full read access; you can complicate it as much as you want, but be warned that it can getquite confusing!31Download 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 41 and 42: C H A P T E R 2■ ■ ■Centraliz
Page 43 and 44: CHAPTER 2 ■ CENTRALIZING YOUR NET
Page 49: CHAPTER 2 ■ CENTRALIZING YOUR NET
Page 83 and 84: C H A P T E R 3■ ■ ■Monitorin
Page 85 and 86: CHAPTER 3 ■ MONITORING AND UPDATI
Page 101 and 102:
CHAPTER 3 ■ MONITORING AND UPDATI
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:
Page 139 and 140:
C H A P T E R 5■ ■ ■Working w
Page 141 and 142:
CHAPTER 5 ■ WORKING WITH FILESYST
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
C H A P T E R 6■ ■ ■Securing
Page 157 and 158:
CHAPTER 6 ■ SECURING YOUR SYSTEMS
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
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 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
CHAPTER 9 ■ WORKING WITH TEXT IN
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
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?