The following figure depicts a simple example network with just the minimum compo-
nents needed to build a Kerberos infrastructure. Depending on the size and topology
of your deployment, you might need to use a different setup.
Figure 6.1
Kerberos Network Topology
TIP: Configuring Subnet Routing
For a setup similar to the one in
Figure 6.1, “Kerberos Network Topology”
(page 89), configure routing between the two subnets (192.168.1.0/24 and
192.168.2.0/24). Refer to Section “Configuring Routing” (Chapter 18, Basic
Networking, ↑Administration Guide) for more information on configuring
routing with YaST.
6.4.2 Choosing the Kerberos Realms
The domain of a Kerberos installation is called a realm and is identified by a name,
such as
EXAMPLE.COM
or simply
ACCOUNTING
. Kerberos is case-sensitive, so
example.com
is actually a different realm than
EXAMPLE.COM
. Use the case you
prefer. It is common practice, however, to use uppercase realm names.
Network Authentication with Kerberos
89
Summary of Contents for LINUX ENTERPRISE DESKTOP 11
Page 1: ...SUSE Linux Enterprise Server www novell com 11 March 17 2009 Security Guide...
Page 9: ...32 7 Managing Audit Event Records Using Keys 433 33 Useful Resources 435...
Page 10: ......
Page 29: ...Part I Authentication...
Page 30: ......
Page 55: ...Figure 4 2 YaST LDAP Server Configuration LDAP A Directory Service 41...
Page 126: ......
Page 127: ...Part II Local Security...
Page 128: ......
Page 158: ......
Page 173: ...Part III Network Security...
Page 174: ......
Page 194: ......
Page 197: ...Figure 16 2 Scenario 2 Figure 16 3 Scenario 3 Configuring VPN Server 183...
Page 210: ......
Page 228: ......
Page 229: ...Part IV Confining Privileges with Novell AppArmor...
Page 230: ......
Page 274: ......
Page 300: ......
Page 328: ......
Page 340: ......
Page 342: ......
Page 386: ......
Page 387: ...Part V The Linux Audit Framework...
Page 388: ......