Re: [ldapext] DBIS - new IETF drafts

Howard Chu <hyc@highlandsun.com> Mon, 13 January 2014 03:00 UTC

Return-Path: <hyc@highlandsun.com>
X-Original-To: ldapext@ietfa.amsl.com
Delivered-To: ldapext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E2561AD8DC for <ldapext@ietfa.amsl.com>; Sun, 12 Jan 2014 19:00:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.54
X-Spam-Level:
X-Spam-Status: No, score=-0.54 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
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 4VT7_4JUaxE0 for <ldapext@ietfa.amsl.com>; Sun, 12 Jan 2014 19:00:02 -0800 (PST)
Received: from mail.highlandsun.com (mail.highlandsun.com [70.87.222.79]) by ietfa.amsl.com (Postfix) with ESMTP id 500C71AD8C4 for <ldapext@ietf.org>; Sun, 12 Jan 2014 19:00:02 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by mail.highlandsun.com (Postfix) with ESMTP id 43A8584ECD; Sun, 12 Jan 2014 21:59:49 -0500 (EST)
Message-ID: <52D356A4.3010508@highlandsun.com>
Date: Sun, 12 Jan 2014 18:59:48 -0800
From: Howard Chu <hyc@highlandsun.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:29.0) Gecko/20100101 Firefox/29.0 SeaMonkey/2.26a1
MIME-Version: 1.0
To: Charlie <medievalist@gmail.com>, Mark R Bannister <dbis@proseconsulting.co.uk>, ldapext <ldapext@ietf.org>
References: <1389133522.4574.30.camel@sorbet.thuis.net> <52CD9F94.2090707@stroeder.com> <52CDC249.8050407@proseconsulting.co.uk> <CAJb3uA6mXTXvBtFc1W=_eCYbfEgGJibdwu1zxU4BtiZvCw6-zg@mail.gmail.com>
In-Reply-To: <CAJb3uA6mXTXvBtFc1W=_eCYbfEgGJibdwu1zxU4BtiZvCw6-zg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [ldapext] DBIS - new IETF drafts
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ldapext>, <mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ldapext/>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ldapext>, <mailto:ldapext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jan 2014 03:00:04 -0000

Charlie wrote:
> What I have learned from about a decade of quietly following LDAP
> across multiple forums and lists is the following:

> 2) POSIX group semantics are the bane of open-source LDAP.  The
> functional paradigm that a member is an attribute of a group is
> fundamentally broken; group membership is an attribute of the member.
> The security concerns frequently raised concerning this are all either
> trivially solvable or pragmatically completely bogus.

Sorry but that makes no sense. It's the same as saying 'element e is a member 
of set S' is true but 'set S contains element e' is false. If one is true then 
both must be true.

Of course there are two different ways to view it. From a sysadmin's point of 
view, what is important is knowing which users are the member of a group. From 
an individual user's point of view, knowing which groups they belong to is 
more important. In real life, users will login many times more frequently than 
sysadmins will manipulate group memberships, so you may decide that optimizing 
for the user check is more important. But while sysadmin manipulation may be 
infrequent, the consequences of making a mistake are high, so data models up 
till now have been designed to make the sysadmin view more straightforward. 
Complexity for the user's perspective is simple to automate and never have to 
worry about ever again.

I think it would be a mistake to lose sight of this distinction.

-- 
   -- Howard Chu
   CTO, Symas Corp.           http://www.symas.com
   Director, Highland Sun     http://highlandsun.com/hyc/
   Chief Architect, OpenLDAP  http://www.openldap.org/project/