1: [[!tag kerberos howto]]
3: #### Why enable Kerberos on your system?
5: Convenience and security. With
6: [Kerberos](http://web.mit.edu/Kerberos/dialogue.html), a single
7: login grants access to all NetBSD web services. Configuration is easy
8: and you only have to do it once (sometimes less).
10: #### [[!toggle id="macosx" text="Mac OS X"]]
11: [[!toggleable id="macosx" text="""
12: OS X autodiscovers and uses the NETBSD.ORG KDC as defined in DNS.
13: To use Kerberized TNF services, log in with your Kerberos [[password]]:
15: `$ kinit <username>@NETBSD.ORG`
17: The right-hand side is a Kerberos realm, not a DNS domain. Case is significant!
20: #### [[!toggle id="netbsd" text="NetBSD"]]
21: [[!toggleable id="netbsd" text="""
22: NetBSD needs to be configured to prevent Kerberos from being used
23: to log into _your_ system, and then to enable Kerberos.
25: 7. Either disable Kerberos auth for `sshd`, `login`, etc. in
26: `/etc/pam.d`, or tell your relevant services not to use PAM.
28: /!\ Disabling KerberosAuthentication in `/etc/ssh/sshd_config` does **NOT** prevent `sshd` from invoking `pam_krb5.so` and prompting for a Kerberos password -- oops. Since you probably do not have a host key in the realm NETBSD.ORG you have little to fear from ssh's KerberosAuthentication method -- nothing can get tickets to use your machine, because there is no host instance for your machine shared between the NetBSD kerberos server and your local keytab. So, the bottom line: turn off UsePAM for `sshd` or adjust your PAM configuration; don't worry about KerberosAuthentication or GSSAPIAuthentication in `sshd` itself.
30: 7. Create `/etc/krb5.conf` containing only the line `[libdefaults]`.
32: NetBSD will now autodiscover and uses the NETBSD.ORG KDC as defined
33: in DNS. To use Kerberized TNF services, log in with your Kerberos
36: `$ kinit <username>@NETBSD.ORG`
38: The right-hand side is a Kerberos realm, not a DNS domain. Case is significant!
41: #### [[!toggle id="windows" text="Windows XP"]]
42: [[!toggleable id="windows" text="""
44: Windows does not provide an easy way to configure and use KDCs different from the one embedded into an Active Directory.
46: Therefore, to use [[Kerberos]], you should follow the following steps:
48: 7. Download the [MIT Kerberos for Windows](http://web.mit.edu/Kerberos/dist/#kfw-3.2) installer. It is composed of different tools traditionally found with Kerberos distributions, like [[!template id=man name=kinit section=1]] or [[!template id=man name=klist section=1]], and a Network Identity Manager, an application used to manage credential caching of Kerberos tickets.
50: 7. Install the package. Use the default provided options, then restart the computer.
52: 7. The Network Identity Manager [(PDF)](http://web.mit.edu/kerberos/kfw-3.2/kfw-3.2.2/netidmgr_userdoc.pdf) should automatically start when you login. As there is no principal currently configured, it should open a dialog box to obtain the new credentials.
54: 7. Enter your principal:
56: Username: <username>
57: Realm: NETBSD.ORG
59: 7. Click `Ok`. After a few seconds, it should obtain the TGT for you from NetBSD.ORG KDC.
CVSweb for NetBSD wikisrc <wikimaster@NetBSD.org> software: FreeBSD-CVSweb