RFC 2623 on NFS Security, RPCSEC_GSS, and Kerberos V5

RFC Editor <rfc-ed@ISI.EDU> Sat, 26 June 1999 01:02 UTC

Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA09094; Fri, 25 Jun 1999 21:02:27 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id UAA15356 for ietf-123-outbound.10@ietf.org; Fri, 25 Jun 1999 20:55:02 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id UAA15194 for <all-ietf@loki.ietf.org>; Fri, 25 Jun 1999 20:21:27 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA08377 for <all-ietf@ietf.org>; Fri, 25 Jun 1999 20:17:28 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id RAA14972; Fri, 25 Jun 1999 17:17:28 -0700 (PDT)
Message-Id: <199906260017.RAA14972@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2623 on NFS Security, RPCSEC_GSS, and Kerberos V5
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Fri, 25 Jun 1999 17:17:28 -0700
From: RFC Editor <rfc-ed@ISI.EDU>

A new Request for Comments is now available in online RFC libraries.


        
	RFC 2623:

        Title:	    NFS Version 2 and Version 3 Security Issues and
		    the NFS Protocol's Use of RPCSEC_GSS and 
		    Kerberos V5
	Author(s):  M. Eisler
        Status:     Proposed Standard
	Date:       June 1999
        Mailbox:    mre@eng.sun.com
        Pages:      19
        Characters: 42521
	Updates/Obsoletes/See Also: None 
        I-D Tag:    draft-ietf-nfsv4-nfssec-01.txt

        URL:        ftp://ftp.isi.edu/in-notes/rfcrfc2623.txt


This memorandum clarifies various security issues involving the NFS
protocol (Version 2 and Version 3 only) and then describes how the
Version 2 and Version 3 of the NFS protocol use the RPCSEC_GSS
security flavor protocol and Kerberos V5.  This memorandum is
provided so that people can write compatible implementations.

This document is a product of the Network File System Version 4
Working Group of the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Alegre Ramos
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
ftp://ftp.isi.edu/in-notes/rfcrfc2623.txt"><ftp://ftp.isi.edu/in-notes/rfcrfc2623.txt>