Return to system.mdwn CVS log

Up to [NetBSD Developer Wiki] / wikisrc / kerberos

web commit by jdf: Move NetBSD to the top (above MacOS), substitute toggling by ordinary sections/headers

    1: [[!tag kerberos howto]]
    2: 
    3: ## Why enable Kerberos on your system?
    4: 
    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).
    9: 
   10: 
   11: ## NetBSD
   12: 
   13: NetBSD needs to be configured to prevent Kerberos from being used
   14: to log into _your_ system, and then to enable Kerberos.
   15: 
   16: 7. Either disable Kerberos auth for `sshd`, `login`, etc. in
   17: `/etc/pam.d`, or tell your relevant services not to use PAM.
   18: 
   19:    /!\ 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.
   20: 
   21: 7. Create `/etc/krb5.conf` containing only the line `[libdefaults]`.
   22: 
   23: NetBSD will now autodiscover and uses the NETBSD.ORG KDC as defined
   24: in DNS. To use Kerberized TNF services, log in with your Kerberos
   25: [[password]]:
   26: 
   27: `$ kinit <username>@NETBSD.ORG`
   28: 
   29: The right-hand side is a Kerberos realm, not a DNS domain. Case is significant!
   30: 
   31: 
   32: ## MacOSX
   33: 
   34: OS X autodiscovers and uses the NETBSD.ORG KDC as defined in DNS.
   35: To use Kerberized TNF services, log in with your Kerberos [[password]]:
   36: 
   37: `$ kinit <username>@NETBSD.ORG`
   38: 
   39: The right-hand side is a Kerberos realm, not a DNS domain. Case is significant!
   40: 
   41: ### A Keychain.app trick
   42: 
   43: To pop up a GUI password dialog:
   44: 
   45: `$ kinit <username>@NETBSD.ORG </dev/null`
   46: 
   47: Check "Remember this password in my keychain" to make future Kerberos
   48: logins (sans input redirection) prompt-free.
   49: 
   50: 
   51: ## Windows XP
   52: 
   53: Windows does not provide an easy way to configure and use KDCs different from the one embedded into an Active Directory.
   54: 
   55: Therefore, to use [[Kerberos]], you should follow the following steps:
   56: 
   57: 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.
   58: 
   59: 7. Install the package. Use the default provided options, then restart the computer.
   60: 
   61: 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.
   62: 
   63: 7. Enter your principal:
   64: 
   65:         Username: <username>
   66:         Realm: NETBSD.ORG
   67: 
   68: 7. Click `Ok`. After a few seconds, it should obtain the TGT for you from NetBSD.ORG KDC.