action #25704
closed
Use kerberos authentication for nfs shares
Added by ingogoeppert over 7 years ago.
Updated over 3 years ago.
Description
To improve security when nfs shares are used, we should use kerberos authentication.
Needs:
- Modified share configuration
- SPNs
- Modified client configuration
Links:
Current state:
- invis Server 14 setup is prepared for kerberos, but exports are still without
- membermod adds the spn we need for kerberos (execute manual)
- client setup is prepared for kerberos. Todo: Exporting the additional spn to the client keytab after the join (or do it manual).
Export keytab on the client: "net ads keytab create" or "net ads keytab create -P"
Files
- Description updated (diff)
- Category changed from 364 to Developement
- Project changed from invis-server to invisAD-setup
- Category deleted (
Developement)
- Target version deleted (
Next)
- Target version set to Future
- Assignee set to ingogoeppert
First setup was successful. Steps to modify a classic nfs setup to a kerberos setup are described in German in the attached document. Test setup was a invis 15 Server and a openSUSE Leap 42.3 Client with KDE Desktop. Both VirtualBox VMs.
- Private changed from Yes to No
- Description updated (diff)
Tests at FrOSCon 13 failed with "permission denied". Very strange: after restarting sssd in the running system it succeeds. It also happened at my test setup. We have to find out why before we roll out nfs with kerberos as default or reconfigure systems to nfs with kerberos.
- Description updated (diff)
- Description updated (diff)
File /etc/sysconfig/nfs did not contain the variable NFS_SECURITY_GSS in openSUSE leap 15.0. We have to investigate this.
- Status changed from In Progress to Closed
- Target version changed from Future to 14.2
First steps done, was not used in production setups until now.
- % Done changed from 30 to 100
Also available in: Atom
PDF