draft-ietf-nfsv4-rpcsec-gssv3-16.txt   draft-ietf-nfsv4-rpcsec-gssv3-17.txt 
NFSv4 W. Adamson NFSv4 W. Adamson
Internet-Draft NetApp Internet-Draft NetApp
Intended status: Standards Track N. Williams Intended status: Standards Track N. Williams
Expires: July 24, 2016 Cryptonector Expires: July 31, 2016 Cryptonector
January 21, 2016 January 28, 2016
Remote Procedure Call (RPC) Security Version 3 Remote Procedure Call (RPC) Security Version 3
draft-ietf-nfsv4-rpcsec-gssv3-16 draft-ietf-nfsv4-rpcsec-gssv3-17
Abstract Abstract
This document specifies version 3 of the Remote Procedure Call (RPC) This document specifies version 3 of the Remote Procedure Call (RPC)
security protocol (RPCSEC_GSS). This protocol provides support for security protocol (RPCSEC_GSS). This protocol provides support for
multi-principal authentication of client hosts and user principals to multi-principal authentication of client hosts and user principals to
a server (constructed by generic composition), security label a server (constructed by generic composition), security label
assertions for multi-level and type enforcement, structured privilege assertions for multi-level and type enforcement, structured privilege
assertions, and channel bindings. assertions, and channel bindings.
skipping to change at page 1, line 42 skipping to change at page 1, line 42
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on July 24, 2016. This Internet-Draft will expire on July 31, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 13, line 25 skipping to change at page 13, line 25
The child context handle returned by a successful multi-principal The child context handle returned by a successful multi-principal
assertion binds the inner RPCSEC_GSSv3 context handle to the parent assertion binds the inner RPCSEC_GSSv3 context handle to the parent
RPCSEC_GSS context and MUST be treated by servers as authenticating RPCSEC_GSS context and MUST be treated by servers as authenticating
the GSS-API initiator principal authenticated by the inner context the GSS-API initiator principal authenticated by the inner context
handle's GSS-API security context. This principal may be mapped to a handle's GSS-API security context. This principal may be mapped to a
server-side notion of user or principal. server-side notion of user or principal.
Multi-principal binding is done by including an assertion of type Multi-principal binding is done by including an assertion of type
rgss3_gss_mp_auth in the RPCSEC_GSS_CREATE rgss3_create_args call rgss3_gss_mp_auth in the RPCSEC_GSS_CREATE rgss3_create_args call
data. The inner context handle is placed in the rgmp_handle field. data. The inner context handle is placed in the rgmp_handle field.
A MIC of the RPC call header up to and including the credential plus A MIC of the RPC call header up to and including the credential is
the GSS security mechanism client host principal name is computed computed using the GSS-API security context associated with the inner
using the GSS-API security context associated with the inner context context handle and is placed in rgmp_rpcheader_mic field. Note that
handle and is placed in rgmp_rpcheader_mic field. the rgmp_rpcheader_mic only identifies the client host GSS context by
it's context handle (the parent context handle) in the rpc header.
An RPCSEC_GSS_CREATE control procedure with a multi-principal
authentication payload MUST use the rpc_gss_svc_privacy security
service for protection. This is to prevent an attacker from
intercepting the RPCSEC_GSS_CREATE control procedure, re-assigning
the (parent) context handle, and stealing the user's identity.
The target verifies the multi-principal authentication by first The target verifies the multi-principal authentication by first
confirming that the parent context used is an RPC client host confirming that the parent context used is an RPC client host
context, and then verifies the rgmp_rpcheader_mic using the GSS-API context, and then verifies the rgmp_rpcheader_mic using the GSS-API
security context associated with the rgmp_handle field. security context associated with the rgmp_handle field.
On a successful verification, the rgss3_gss_mp_auth field in the On a successful verification, the rgss3_gss_mp_auth field in the
rgss3_create_res reply MUST be filled in with the inner RPCSEC_GSSv3 rgss3_create_res reply MUST be filled in with the inner RPCSEC_GSSv3
context handle as the rgmp_handle, and a MIC computed over the RPC context handle as the rgmp_handle, and a MIC computed over the RPC
reply header (see section Section 2.3) using the GSS-API security reply header (see section Section 2.3) using the GSS-API security
 End of changes. 4 change blocks. 
8 lines changed or deleted 15 lines changed or added

This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/