SEAM Interoperability with MIT

SEAM interoperates with an MIT installation with the following caveats:

1. gkadmin and kadmin do not work against MIT KDCs. The reason for this failure is that gkadmin and kadmin use the RPCSEC_GSS protocol to secure the connection to the KDC. The MIT Kerberos V5 1.0 installation uses a non-standard AUTH_GSSAPI protocol to provide security. Because these two protocols are different, you cannot use gkadmin and kadmin with an MIT KDC.

2. SEAM does not include the ksu command. Instead, PAM is used to let su do most of what ksu does. One area that is different is that ksu looks at the .k5login file to see if the user using su is allowed to do so without a password, if he has Kerberos V5 credentials. This check is not done in SEAM.

3. SEAM and MIT Kerberos V5 code are not intended to co-exist on the same host. While this is theoritically possible, it is not supported.

4. SEAM requires that rpcbind be run. This is not a requirement of the MIT Kerberos V5 installation.