IETF Logo Mail Archive

Re: [secdir] [nfsv4] SECDIR Review of draft-ietf-nfsv4-umask-03

Nico Williams <nico@cryptonector.com> Sat, 03 June 2017 01:06 UTC

Return-Path: <nico@cryptonector.com>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E75FE129473; Fri, 2 Jun 2017 18:06:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.5
X-Spam-Level:
X-Spam-Status: No, score=-1.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_SORBS_SPAM=0.5] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WWmcg4rirHZ1; Fri, 2 Jun 2017 18:06:07 -0700 (PDT)
Received: from homiemail-a66.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 44AED129470; Fri, 2 Jun 2017 18:06:07 -0700 (PDT)
Received: from homiemail-a66.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a66.g.dreamhost.com (Postfix) with ESMTP id AAF5DC002824; Fri, 2 Jun 2017 18:06:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=T5UDZivlH7Oz5w xoM19910BuRvs=; b=Hl+9ZOeXEgYu6Kie++3f+sweI/fLL27RFKcOBod0i1qrny MRsWAzh7Hw3+Ysp+M+Ofi7r1R0FATalhcyymLkqMQMVBSynyUViOOHV+PVPhzD72 edvAtsBx1NSWrdGQghevTzTWqSN/iLodHx1w/3aLtNTv9HjJ+P+F3iZ/23Yng=
Received: from localhost (cpe-70-123-158-140.austin.res.rr.com [70.123.158.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a66.g.dreamhost.com (Postfix) with ESMTPSA id 3A891C002823; Fri, 2 Jun 2017 18:06:06 -0700 (PDT)
Date: Fri, 02 Jun 2017 20:06:02 -0500
From: Nico Williams <nico@cryptonector.com>
To: Phillip Hallam-Baker <phill@hallambaker.com>
Cc: David Noveck <davenoveck@gmail.com>, "secdir@ietf.org" <secdir@ietf.org>, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, NFSv4 <nfsv4@ietf.org>
Message-ID: <20170603010601.GD2903@localhost>
References: <CAMm+Lwh+E+BsATQmmX6ccJou-sz1XNtFHxQZikohYCeT0qkfdQ@mail.gmail.com> <CAKKJt-fsJ1UinNiW2LitxVQT4M1YqnFF+1cygU132=bQNgiUnA@mail.gmail.com> <CADaq8jd+6gN2H0QWC+dM-e3pb1gUJKLE7=8PPpprGGKBQZhueg@mail.gmail.com> <CAMm+Lwgw0fwXa4Gd0nm_d+mwvkfeM8gq9=ROLRqhHyTO-pjeRQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAMm+Lwgw0fwXa4Gd0nm_d+mwvkfeM8gq9=ROLRqhHyTO-pjeRQ@mail.gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/Ak5r6U78f1MJmKlTcfzkvIoxM6Q>
Subject: Re: [secdir] [nfsv4] SECDIR Review of draft-ietf-nfsv4-umask-03
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdir/>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Jun 2017 01:06:08 -0000

On Fri, Jun 02, 2017 at 08:32:15PM -0400, Phillip Hallam-Baker wrote:
> On Wed, May 31, 2017 at 9:23 AM, David Noveck <davenoveck@gmail.com> wrote:
> Instead of using GSS which is a framework for fifty shades of almost always
> password auth, I would move to authenticating and encrypting using public
> key based credentials.

What are you on about??

GSS-API has a number of mechanisms, including:

 - Kerberos V5 [RFC4121]

 - PKU2U, which is PKIX based (no reference, as it's not yet
   standardized at the IETF)

 - SCRAM (password based)

and others.

Nico
--

v2.23.0 | Report a Bug | By Email