One thing that is very hard to track through the RFCs and other documents. Does NFSv4 encrypt just the authentication interactions or can it encrypt all of the server to server interactions.
NFSv4 is a client to server protcol. Cryptographic technology (via RPCSEC_GSS) can be used authenticate users on clients to servers, as well as provided secure integrity checksums to prevent an attacker from tampering with the NFS requests or responses. Via RPCSEC_GSS one can also encrypt all requests and responses.
I co-authored RFC3530, the NFSv4.0 specification and RFC5661 the NFSv4.1 specification. I work for NetApp on NFS and things related to NFS. I was the primary author for RFC2203, which adds real security to NFS, and led the SEAM project at Sun that produced the first NFS implementation that used Kerberos V5 authentication.
2 Comments:
One thing that is very hard to track through the RFCs and other documents. Does NFSv4 encrypt just the authentication interactions or can it encrypt all of the server to server interactions.
Art,
NFSv4 is a client to server protcol.
Cryptographic technology (via RPCSEC_GSS) can be used authenticate users on clients to servers, as well
as provided secure integrity checksums to prevent an attacker from tampering with the NFS requests or responses. Via RPCSEC_GSS one can also encrypt all requests and responses.
NFSv4 has no server-to-server
interactions.
Post a Comment
<< Home