NFS + Kerberos
Rick Macklem
rmacklem at uoguelph.ca
Sat Feb 9 16:02:29 UTC 2013
Monchil Ivanov wrote:
> Hello,
>
> I have been trying to follow this guide [1] to get NFS with Kerberos
> working on FreeBSD, but I have some trouble. I hope somebody has the
> time and desire to help me...
>
> I am using FreeBSD 9.1 as NFS server with the following configuration
> on the server:
>
> file /etc/krb5.conf:
>
> [libdefaults]
> default_realm = EXAMPLE.LOCAL
> default_etypes = des-cbc-crc
> default_etypes_des = des-cbc-crc
> allow_weak_crypto = true
> [realms]
> EXAMPLE.LOCAL = {
> kdc = kerberos.example.local
> admin_server = kerberos.example.local
> }
> [domain_realm]
> .example.local = EXAMPLE.LOCAL
>
> file /etc/exports:
>
> V4: / -sec=krb5i:krb5p
> /tank/storage -sec=krb5i:krb5p
>
For ZFS every ZFS volume below the "V4: <root>" normally needs
to be exported. Below you mention that the NFSv4 mount worked
for -sec=sys, but I don't know how it would.
Assuming /tank is ZFS (if it's UFS, just ignore this;-), I'd
suggest changing the line to:
V4: /tank/storage -sec=krb5i,krb5p
(You then need to use srv.example.local:/ as your mount point
for the mount command for NFSv4.)
> file /etc/rc.conf:
>
> ## nfsv4
> nfs_server_enable="YES"
> nfsv4_server_enable="YES"
> nfsuserd_enable="YES"
> mountd_enable="YES"
> mountd_flags="-r -n"
>
> # for kerberos
> gssd_enable="YES"
>
> kerberos seems to be working:
>
> root at srv:/root # kinit -k nfs/srv.example.local
> root at srv:/root # klist
> Credentials cache: FILE:/tmp/krb5cc_0
> Principal: nfs/srv.example.local at EXAMPLE.LOCAL
>
> Issued Expires Principal
> Feb 2 21:04:02 Feb 3 07:04:02 krbtgt/EXAMPLE.LOCAL at EXAMPLE.LOCAL
> root at srv:/root # kdestroy
> root at srv:/root # ktutil list
> FILE:/etc/krb5.keytab:
>
> Vno Type Principal
> 1 des-cbc-crc nfs/srv.example.local at EXAMPLE.LOCAL
>
> krb4:/etc/srvtab:
>
> Vno Type Principal
>
> the client is FreeBSD 8.2 with the following configuration:
>
> file /etc/krb5.conf:
>
> [libdefaults]
> default_realm = EXAMPLE.LOCAL
> default_etypes = des-cbc-crc
> default_etypes_des = des-cbc-crc
> allow_weak_crypto = true
> [realms]
> EXAMPLE.LOCAL = {
> kdc = kerberos.example.local
> admin_server = kerberos.example.local
> }
> [domain_realm]
> .example.local = EXAMPLE.LOCAL
>
> file /etc/rc.conf:
>
> ## NFS v4
> nfsuserd_enable="YES"
> nfscbd_enable="YES"
> # kerberos
> gssd_enable="YES"
>
> file /etc/sysctl.conf:
> # Allow normal users to mount filesystems.
> vfs.usermount=1
>
> here is the output from the client:
>
> $ klist
> klist: No ticket file: /tmp/krb5cc_1001
>
> $ mount -t nfs -o nfsv4,soft,sec=krb5i srv.example.local:/tank/storage
> /mnt/srv
> mount_nfs: can't update /var/db/mounttab for
> srv.example.local:/tank/storage
> nfsv4 err=10016
> mount_nfs: /mnt/srv, : Input/output error
>
Yep, I would expect this to fail.
> then I do:
>
> $ kinit user
> $ klist
> Credentials cache: FILE:/tmp/krb5cc_1001
> Principal: user at EXAMPLE.LOCAL
>
> Issued Expires Principal
> Feb 2 21:15:36 Feb 3 07:15:33 krbtgt/EXAMPLE.LOCAL at EXAMPLE.LOCAL
>
> $ mount -t nfs -o nfsv4,soft,sec=krb5i srv.example.local:/tank/storage
> /mnt/srv
> mount_nfs: can't update /var/db/mounttab for
> srv.example.local:/tank/storage
This error message happens because the non-root user doesn`t have
write access mounttab. You can fix the problem by opening up
permissions on it, but it does not really matter. The contents of
mounttab is for information only and does not affect the mount.
> nfsv4 err=10016
> mount_nfs: /mnt/srv, : Input/output error
>
Not sure why this fails. Might have been the issue I mentioned above.
I`d suggest you try again with the above V4: line modified and the
mount looking like:
$ mount -t nfs -o nfsv4,sec=krb5i srv.example.local:/ /mnt/srv
(I also strongly recommend against using `soft` for NFSv4 mounts, but
that shouldn`t cause this to fail.)
10016 is NFS4ERR_WRONGSEC, so it didn`t like you using Kerberos. I
suspect that would be somewhere higher up in the path.
> $ klist
> Credentials cache: FILE:/tmp/krb5cc_1001
> Principal: user at EXAMPLE.LOCAL
>
> Issued Expires Principal
> Feb 2 21:15:36 Feb 3 07:15:33 krbtgt/EXAMPLE.LOCAL at EXAMPLE.LOCAL
> Feb 2 21:15:43 Feb 3 07:15:33 nfs/srv.example.local at EXAMPLE.LOCAL
>
> Note: the mount works without Kerberos if I add "sys" to the "sec"
> option on both lines of /etc/exports, ownership works too, therefore I
> think that nfsv4 works, nfsv3 works too. However I have no idea why
> they don't work with Kerberos.
>
I was never sure it was the correct thing to do, but the original author
coded it so that it would fall back to -sec=sys when Kerberos failed.
That would explain why it succeeds for this case.
> Note: With and without a kerberos ticket, the result when using nfsv3
> is:
>
> $ mount -t nfs -o nfsv3,soft,sec=krb5i srv.example.local:/tank/storage
> /mnt/srv
> mount_nfs: can't update /var/db/mounttab for
> srv.example.local:/tank/storage
>
> $ ls /mnt/srv
> ls: /mnt/srv: Permission denied
I have never tried a non-root NFSv3 Kerberos mount. Normally, the above
mount would be done by root and then accessed by the non-root user.
(NFSv3 has no state-related operations, so the mount can be done by
root, since it does not need kerberos authentication.) I cannot think
of why a non-root mount would not work, but since I have never done it,
I would suggest you try doing this mount as root and see if it makes any
difference.
In general, the cause of these failures can be difficult to figure out,
since it can fail in so many ways. Looking at the log file for the KDC
can sometimes help. Or, capturing packets and looking at them in
wireshark (which understands NFSv4 and RPCSEC_GSS) will give you some idea
where it breaks.
Good luck with it, rick
>
> Is there an easy way to get it working? Am I doing something wrong?
>
> PS: Please CC me, since I am not subscribed.
>
> 1: http://code.google.com/p/macnfsv4/wiki/FreeBSD8KerberizedNFSSetup
>
> Regards,
> Momchil
> _______________________________________________
> freebsd-fs at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-fs
> To unsubscribe, send any mail to "freebsd-fs-unsubscribe at freebsd.org"
More information about the freebsd-fs
mailing list