AUTH
Click on the red underlined text to get to the source
... AUTH_SYS ...
... encryption and Kerberos secret keys (and tickets) in the AUTH_KERB4
case. Again, the server and client must agree on the identity ...
... operating system independent than the user identifier and group
identifier mapping in AUTH_SYS. Also, because the authentication
parameters are encrypted ...
... be authenticated with a flavor stronger than AUTH_SYS. This is a
problem because the RPCSEC_GSS protocol uses NULL for control
messages ...
... accept the NULL procedure ping over AUTH_NONE and AUTH_SYS, in
addition to other RPC security ...
... often the case that, for unattended operation in concert with an
automounter [Callaghan], the AUTH_DH, AUTH_KERB4, or RPCSEC_GSS ...
... client will use
AUTH_NONE or AUTH_SYS for the initial NFS operations used to mount a
file system ...
...
If a client uses AUTH_NONE, the server's options are the same as the
above, except that AUTH_NONE carries with it no user identity ...
... client uses AUTH_NONE, the server's options are the same as the
above, except that AUTH_NONE carries with it no user identity. In
order to allow the request, on many operating systems ...
... attacker must still be able
impersonate a user's credentials, which is simple for AUTH_SYS,
but harder for AUTH_DH ...
... credentials, which is simple for AUTH_SYS,
but harder for AUTH_DH, AUTH_KERB4, and RPCSEC_GSS ...
... pseudo flavor number, an ASCII string name for the flavor
(for example "none" has been assigned for AUTH_NONE), and
...
... Protocol Specification Version 2", RFC 1057, June 1988. This RFC is being referenced for its description of the AUTH_DH (AUTH_DES ...
... 1057, June 1988. This RFC is being referenced for its description of the AUTH_DH (AUTH_DES) RPC security ...