Expand description
NFS version 2 – RFC 1094.
All 18 procedures. The version is long obsolete and still enabled on plenty of servers, which is exactly why it matters: it is the weakest of the three by a wide margin.
- No security negotiation at all (RFC 2623 sec. 2.7). The server cannot advertise, and the client cannot request, anything beyond AUTH_SYS.
- No
ACCESSprocedure. NFSv3 added it so a client could ask what it would be permitted to do; under v2 a client simply tries the operation. - Fixed 32-byte file handles with no length prefix (
FHSIZE = 32, RFC 1094 sec. 2.3.3), unlike NFSv3’s variable-length handle. That changes the XDR encoding, which is why these types cannot share NFSv3’s.
Some servers apply root_squash on their v3 path but not their v2 path, so
where both are offered v2 is worth probing first.
Re-exports§
pub use raw::Nfs2RawClient;pub use wire::NFS_PROGRAM as PROGRAM;pub use wire::NFS_VERSION as VERSION;pub use wire::Nfs2FileAttr;pub use wire::Nfs2FileHandle;pub use wire::Nfs2SetAttr;pub use wire::Nfs2Stat;
Modules§
Structs§
- Nfs2
Client - Client for the
NFSv2service (program 100003, version 2).
Enums§
- Nfs2
Error - An NFSv2 operation failed.
Type Aliases§
- Mount
V1Client - Re-export the MOUNT client from
nfswolf-mountfor backward compatibility.