[nfsv4] NFSv4 Persistent Mounts and Authentication
Lesley Kimmel <lesley.j.kimmel@gmail.com> Tue, 20 June 2017 12:37 UTC
Return-Path: <lesley.j.kimmel@gmail.com>
X-Original-To: nfsv4@ietfa.amsl.com
Delivered-To: nfsv4@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5004912EAF0 for <nfsv4@ietfa.amsl.com>; Tue, 20 Jun 2017 05:37:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 NHf7cQfbAUtp for <nfsv4@ietfa.amsl.com>; Tue, 20 Jun 2017 05:37:16 -0700 (PDT)
Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com [IPv6:2a00:1450:400c:c09::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CC82A12EA8D for <nfsv4@ietf.org>; Tue, 20 Jun 2017 05:37:01 -0700 (PDT)
Received: by mail-wm0-x234.google.com with SMTP id d73so18890081wma.0 for <nfsv4@ietf.org>; Tue, 20 Jun 2017 05:37:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=pyujpcO/FCraqBSuLFbiSAcaJH+GO+hR0BvQzHvc6JA=; b=Ug2ACLwZ1ra5kiliAwb2GUdLjN75T8XenXzXNdlJ2vEJr5vp1N5orFGmQV4o7ita9S qQxTphlyhXy73k0Q/4tUZOBUVLaxbjx1vpOSh0p4bZU71kyMkUHaSAHDsCAlu7HnNYMq 3hYo/wApKlBEIuVxrLfEqv49oRAckivsgkii3N05xmROSCtxWiJZQXJF/btQowwqLTGe QYC4jq4gLjf1I6EqlOODaT1yf4EdIm7k42jawQ7EIqz6cXO8rSar8jby0ZPCTVETpNzH b98r7lp8xSjYej+uG+pfca4084OVOKb91KHU33DFny0vKOiiaHCSpm4+DdeG5YhDWwgE uitQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=pyujpcO/FCraqBSuLFbiSAcaJH+GO+hR0BvQzHvc6JA=; b=b1cSIRmvJTZTG7Iei/jnGUIsQ+H6K8zntH1i1e8rxNXoEjaT0+m2GDNp9h+DX3TNA3 /fFl3cdTb/2XIosTISxnxvZqZOKSkDvJ1ppVSxxuOeXvjKV6mRZZMdd+m/5aHb3hhHnp hBMOsMUEW+KyQLX08MtJhq6xnkvnH9YZWrTcwWwYdzWSe1/M0CNovOlgYfmn9+0QD5Fe GuPyz98/aT196iPsfT+coou4nXk4Pr71M2NxvlzBY+NDLxDVGUfxUpKQEcSy7Jl4uI3p AKb5uxCxbyQFVncXS0uZcECOGlAUTLaL2g6VpIxhYUuSEtVqUeX7OYWE/kjcqIazFs2l Yn1w==
X-Gm-Message-State: AKS2vOyTY9ruAfCvBOXeTq7Ct3g7kcWT6whMP8QfcxloYI/bQegfnWZ3 SRYtLmkeOAiy8NL+EHDS6i1q0Sx3UQ==
X-Received: by 10.80.152.194 with SMTP id j60mr20494885edb.98.1497962220176; Tue, 20 Jun 2017 05:37:00 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.80.182.248 with HTTP; Tue, 20 Jun 2017 05:36:59 -0700 (PDT)
From: Lesley Kimmel <lesley.j.kimmel@gmail.com>
Date: Tue, 20 Jun 2017 07:36:59 -0500
Message-ID: <CAAQu=7QqQFokuuMWAbfw9x2jq2GeoqMpHAV4kJLQoUUjw1QPAA@mail.gmail.com>
To: nfsv4@ietf.org
Content-Type: multipart/alternative; boundary="94eb2c19586405481605526382e4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/_8D0IvzW1a3QjxFROtbGOeAeCb4>
Subject: [nfsv4] NFSv4 Persistent Mounts and Authentication
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nfsv4/>
List-Post: <mailto:nfsv4@ietf.org>
List-Help: <mailto:nfsv4-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Jun 2017 12:37:17 -0000
All; Forgive me if this question is somewhat incorrect as we are just getting started with NFSv4. It seems that [kerberized] NFSv4 is well suited for things like home directories that can be authenticated and mounted when a user accesses the system. However, we are considering a few issues and are wondering what the recommended configuration is: 1) Users execute a long running job (assume longer than the Kerberos ticket lifetime) and log out. How can the Kerberos ticket automatically be renewed so that these types of jobs continue to run? 2) How would CRON jobs executing scripts from an NFS share gain a Kerberos ticket to be able to perform these actions? Thanks ahead of time, -Lesley Kimmel
- [nfsv4] NFSv4 Persistent Mounts and Authentication Lesley Kimmel
- Re: [nfsv4] NFSv4 Persistent Mounts and Authentic… Benjamin Kaduk