Federated Filesystem Security Addendum
draft-cel-nfsv4-federated-fs-security-addendum-06

Document Type Active Internet-Draft (individual)
Last updated 2016-10-25
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network File System Version 4                                   C. Lever
Internet-Draft                                                    Oracle
Intended status: Standards Track                        October 25, 2016
Expires: April 28, 2017

                 Federated Filesystem Security Addendum
           draft-cel-nfsv4-federated-fs-security-addendum-06

Abstract

   This document addresses critical security-related items that are
   missing from existing FedFS Proposed Standards.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on April 28, 2017.

Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must

Lever                    Expires April 28, 2017                 [Page 1]
Internet-Draft           FedFS Security Addendum            October 2016

   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Problem Statement: GSSAPI service name for ADMIN  . . . .   2
     1.2.  Problem Statement: GSSAPI service name for NSDB . . . . .   3
     1.3.  Problem Statement: Compromised NSDBs  . . . . . . . . . .   3
   2.  GSSAPI Service Name for the FedFS ADMIN protocol  . . . . . .   4
   3.  GSSAPI Service Name for the FedFS NSDB protocol . . . . . . .   5
     3.1.  Cross-realm considerations  . . . . . . . . . . . . . . .   6
   4.  Fencing Compromised NSDBs . . . . . . . . . . . . . . . . . .   6
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   8
   Appendix A.  Acknowledgements . . . . . . . . . . . . . . . . . .   8
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   Requirements for federated filesystems are described in [RFC5716].
   Specification of the protocol used by administrators to configure
   fileservers and construct namespaces is provided in [RFC7533].
   Specification of the protocol allowing fileservers to store namespace
   information is provided in [RFC7532].

   These documents are now immutable.  However, some security-related
   concerns have arisen that should be addressed immediately rather than
   waiting for another version of these protocols to be ratified.

1.1.  Problem Statement: GSSAPI service name for ADMIN

   After IESG review, the Security Considerations chapter of [RFC7533]
   now specifically requires that implementations of this protocol
   support GSSAPI security mechanisms.

   ADMIN protocol clients must use a service principal to establish a
   GSS context shared with an ADMIN server.  To construct the service
   principal, clients need to know a priori the protocol's GSSAPI
   service name.  The form of that service name is described in section
   4.1 of [RFC2743].

   Also according to the final paragraph of section 4.1, requesting an
   addition to the "GSSAPI/Kerberos/SASL Service Names" registry

Lever                    Expires April 28, 2017                 [Page 2]
Show full document text