Connected: An Internet Encyclopedia
RFC 1831 - 9.1 Null Authentication
Top: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1831
Up: 9. AUTHENTICATION PROTOCOLS
Prev: 9. AUTHENTICATION PROTOCOLS
Next: 10. RECORD MARKING STANDARD
9.1 Null Authentication
Often calls must be made where the client does not care about its
identity or the server does not care who the client is. In this
case, the flavor of the RPC message's credential, verifier, and reply
verifier is "AUTH_NONE". Opaque data associated with "AUTH_NONE" is
undefined. It is recommended that the length of the opaque data be
zero.
Next: 10. RECORD MARKING STANDARD
Connected: An Internet Encyclopedia
RFC 1831 - 9.1 Null Authentication