From ldapext-bounces@ietf.org Wed Mar 01 09:00:24 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FERsM-0003Jl-S4; Wed, 01 Mar 2006 09:00:22 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FERsJ-0003Jg-U7
	for ldapext@ietf.org; Wed, 01 Mar 2006 09:00:20 -0500
Received: from e5.ny.us.ibm.com ([32.97.182.145])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FERsJ-0006ao-CC
	for ldapext@ietf.org; Wed, 01 Mar 2006 09:00:19 -0500
Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [9.56.227.234])
	by e5.ny.us.ibm.com (8.12.11/8.12.11) with ESMTP id k21E0GHN011566
	for <ldapext@ietf.org>; Wed, 1 Mar 2006 09:00:16 -0500
Received: from d01av03.pok.ibm.com (d01av03.pok.ibm.com [9.56.224.217])
	by d01relay02.pok.ibm.com (8.12.10/NCO/VER6.8) with ESMTP id
	k21E0ETf110266 for <ldapext@ietf.org>; Wed, 1 Mar 2006 09:00:16 -0500
Received: from d01av03.pok.ibm.com (loopback [127.0.0.1])
	by d01av03.pok.ibm.com (8.12.11/8.13.3) with ESMTP id k21E0EsY030128
	for <ldapext@ietf.org>; Wed, 1 Mar 2006 09:00:14 -0500
Received: from d27ml001.rchland.ibm.com (d27ml001.rchland.ibm.com
	[9.10.229.77])
	by d01av03.pok.ibm.com (8.12.11/8.12.11) with ESMTP id k21E0EUC030099
	for <ldapext@ietf.org>; Wed, 1 Mar 2006 09:00:14 -0500
In-Reply-To: <7.0.1.0.0.20060228132901.03d38568@OpenLDAP.org>
To: ldapext@ietf.org
Subject: Re: [ldapext] Fwd: I-D ACTION:draft-zeilenga-ldap-managedit-00.txt
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 7.0 HF85 November 04, 2005
From: John McMeeking <jmcmeek@us.ibm.com>
Message-ID: <OFB5A0E890.88D5476C-ON86257124.00486BD7-86257124.004CE95A@us.ibm.com>
Date: Wed, 1 Mar 2006 08:00:10 -0600
X-MIMETrack: Serialize by Router on d27ml001/27/M/IBM(Release 7.0.1|January 17,
	2006) at 03/01/2006 08:00:14 AM,
	Serialize complete at 03/01/2006 08:00:14 AM
X-Spam-Score: 1.3 (+)
X-Scan-Signature: f49c97ce49302a02285a2d36a99eef8c
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1341656204=="
Errors-To: ldapext-bounces@ietf.org

--===============1341656204==
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">I would like to see a name for the control
that is not so close to the existing ManageDsaIT control. &nbsp;I picture
someone using the wrong control because of the similarity in names. &nbsp;Maybe
something along the lines of &quot;repair DIT&quot; or &quot;allow exceptions&quot;?</font>
<br>
<br><font size=2 face="sans-serif">I have occasionally found the need for
such a mechanism.</font>
<br>
<br><font size=2 face="sans-serif">I've always been a little uneasy about
making it too easy to use for fear that an administrator would start using
such a control for one purpose and either use it where it shouldn't have
been used -- like inadvertantly updating an entry on a read-only replica
because he misdiagnosed a problem, or using it to fix one problem and because
of the controls presence also be allowed to do something else unintended.
&nbsp;Or worse yet, just start using the control out of bad habit.</font>
<br>
<br><font size=2 face="sans-serif">I'm trying to think of something that
makes the control perhaps a little less dangerous without making it impossible
to use. &nbsp;In some respects, maybe what I really want is an interactive
&quot;are you sure you want to do this&quot; capability; of course those
always come with a &quot;yes to all&quot; option, so maybe I'm just unduly
paranoid. &nbsp;Maybe there could be a family of controls - one control
for each kind of exceptional action - or a control value indicating the
kind of change intended.</font>
<br>
<br>
<br><font size=2 face="sans-serif">John &nbsp;McMeeking<br>
</font>
<br>
<br><tt><font size=2>&quot;Kurt D. Zeilenga&quot; &lt;Kurt@OpenLDAP.org&gt;
wrote on 02/28/2006 03:30:13 PM:<br>
<br>
&gt; Enjoy! &nbsp;-- Kurt<br>
&gt; <br>
&gt; &gt;To: i-d-announce@ietf.org<br>
&gt; &gt;Cc: <br>
&gt; &gt;From: Internet-Drafts@ietf.org<br>
&gt; &gt;Date: Tue, 28 Feb 2006 15:50:01 -0500<br>
&gt; &gt;Subject: I-D ACTION:draft-zeilenga-ldap-managedit-00.txt <br>
&gt; &gt;Reply-To: internet-drafts@ietf.org<br>
&gt; &gt;<br>
&gt; &gt;A New Internet-Draft is available from the on-line Internet-Drafts
<br>
&gt; directories.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp;Title &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; : The LDAP Manage Directory Information Tree Control<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp;Author(s) &nbsp; &nbsp; &nbsp; : K.
Zeilenga<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp;Filename &nbsp; &nbsp; &nbsp; &nbsp;:
draft-zeilenga-ldap-managedit-00.txt<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp;Pages &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; : 12<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp;Date &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp;: 2006-2-28<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp;<br>
&gt; &gt;This document defines the Lightweight Directory Access Protocol
(LDAP)<br>
&gt; &gt;Manage Directory Information Tree (DIT) Control which allows a<br>
&gt; &gt;directory user agent (a client) to request the directory service<br>
&gt; &gt;temporarily relax enforcement of constraints of the X.500 models.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;A URL for this Internet-Draft is:<br>
&gt; &gt;http://www.ietf.org/internet-drafts/draft-zeilenga-ldap-managedit-00.txt<br>
&gt; &gt;<br>
&gt; &gt;To remove yourself from the I-D Announcement list, send a message
to <br>
&gt; &gt;i-d-announce-request@ietf.org with the word unsubscribe in the
body<br>
&gt; of the message. &nbsp;<br>
&gt; &gt;You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
<br>
&gt; &gt;to change your subscription settings.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;Internet-Drafts are also available by anonymous FTP. Login with
the username<br>
&gt; &gt;&quot;anonymous&quot; and a password of your e-mail address. After
logging in,<br>
&gt; &gt;type &quot;cd internet-drafts&quot; and then<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp;&quot;get draft-zeilenga-ldap-managedit-00.txt&quot;.<br>
&gt; &gt;<br>
&gt; &gt;A list of Internet-Drafts directories can be found in<br>
&gt; &gt;http://www.ietf.org/shadow.html <br>
&gt; &gt;or ftp://ftp.ietf.org/ietf/1shadow-sites.txt<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;Internet-Drafts can also be obtained by e-mail.<br>
&gt; &gt;<br>
&gt; &gt;Send a message to:<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp;mailserv@ietf.org.<br>
&gt; &gt;In the body type:<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp;&quot;FILE /internet-drafts/draft-zeilenga-ldap-managedit-00.txt&quot;.<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp;<br>
&gt; &gt;NOTE: &nbsp; The mail server at ietf.org can return the document
in<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp;MIME-encoded form by using the &quot;mpack&quot;
utility. &nbsp;To use this<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp;feature, insert the command &quot;ENCODING
mime&quot; before the &quot;FILE&quot;<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp;command. &nbsp;To decode the response(s),
you will need &quot;munpack&quot; or<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp;a MIME-compliant mail reader. &nbsp;Different
MIME-compliant mail readers<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp;exhibit different behavior, especially
when dealing with<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp;&quot;multipart&quot; MIME messages
(i.e. documents which have been split<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp;up into multiple messages), so check
your local documentation on<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp;how to manipulate these messages.<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<br>
&gt; &gt;Below is the data which will enable a MIME compliant mail reader<br>
&gt; &gt;implementation to automatically retrieve the ASCII version of
the<br>
&gt; &gt;Internet-Draft.<br>
&gt; &gt;<br>
&gt; &gt;Content-Type: text/plain<br>
&gt; &gt;Content-ID: &lt;2006-2-28130944.I-D@ietf.org&gt;<br>
&gt; &gt;<br>
&gt; &gt;ENCODING mime<br>
&gt; &gt;FILE /internet-drafts/draft-zeilenga-ldap-managedit-00.txt<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;&lt;ftp://ftp.ietf.org/internet-drafts/draft-zeilenga-ldap-managedit-00.txt&gt;<br>
&gt; &gt;_______________________________________________<br>
&gt; &gt;I-D-Announce mailing list<br>
&gt; &gt;I-D-Announce@ietf.org<br>
&gt; &gt;https://www1.ietf.org/mailman/listinfo/i-d-announce<br>
&gt; <br>
&gt; <br>
&gt; _______________________________________________<br>
&gt; Ldapext mailing list<br>
&gt; Ldapext@ietf.org<br>
&gt; https://www1.ietf.org/mailman/listinfo/ldapext<br>
</font></tt>


--===============1341656204==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext

--===============1341656204==--



From ldapext-bounces@ietf.org Wed Mar 01 10:31:37 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FETIe-000182-9T; Wed, 01 Mar 2006 10:31:36 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FETIc-00014r-N8
	for ldapext@ietf.org; Wed, 01 Mar 2006 10:31:34 -0500
Received: from 64-1-124-83.dsl.3u.net ([83.124.1.64]
	helo=srv1.int.stroeder.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FETIb-0002Db-6X
	for ldapext@ietf.org; Wed, 01 Mar 2006 10:31:34 -0500
Received: from localhost (localhost [127.0.0.1])
	by srv1.int.stroeder.com (Postfix) with ESMTP id CDC14326D;
	Wed,  1 Mar 2006 16:31:30 +0100 (CET)
Received: from srv1.int.stroeder.com ([127.0.0.1])
	by localhost (srv1 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
	id 10512-02; Wed,  1 Mar 2006 16:31:23 +0100 (CET)
Received: from [10.1.1.5] (unknown [10.1.1.5])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client CN "Michael Stroeder",
	Issuer "Thawte Personal Freemail Issuing CA" (not verified))
	by srv1.int.stroeder.com (Postfix) with ESMTP id DC73531B6;
	Wed,  1 Mar 2006 16:31:22 +0100 (CET)
Message-ID: <4405BE4A.20808@stroeder.com>
Date: Wed, 01 Mar 2006 16:31:22 +0100
From: =?ISO-8859-1?Q?Michael_Str=F6der?= <michael@stroeder.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050920
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: John McMeeking <jmcmeek@us.ibm.com>
Subject: Re: [ldapext] Fwd: I-D ACTION:draft-zeilenga-ldap-managedit-00.txt
References: <OFB5A0E890.88D5476C-ON86257124.00486BD7-86257124.004CE95A@us.ibm.com>
In-Reply-To: <OFB5A0E890.88D5476C-ON86257124.00486BD7-86257124.004CE95A@us.ibm.com>
X-Enigmail-Version: 0.93.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: amavisd-new at int.stroeder.com
X-Spam-Score: 0.1 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: ldapext@ietf.org
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

John McMeeking wrote:
> 
> I would like to see a name for the control that is not so close to the
> existing ManageDsaIT control.

+1

> I've always been a little uneasy about making it too easy to use for
> fear that an administrator would start using such a control for one
> purpose and either use it where it shouldn't have been used

There are many possibilities for an administrator to do bad things.

> -- like
> inadvertantly updating an entry on a read-only replica because he
> misdiagnosed a problem, or using it to fix one problem and because of
> the controls presence also be allowed to do something else unintended.
>  Or worse yet, just start using the control out of bad habit.

There's no technical solution against dumb people.

> I'm trying to think of something that makes the control perhaps a
> little less dangerous without making it impossible to use. In some
> respects, maybe what I really want is an interactive "are you sure
> you want to do this" capability;

This is subject of client application programming but does not work for
non-interactive clients.

Ciao, Michael.

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Wed Mar 01 12:54:09 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FEVWa-0005fG-7C; Wed, 01 Mar 2006 12:54:08 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FEVWY-0005f1-9G
	for ldapext@ietf.org; Wed, 01 Mar 2006 12:54:06 -0500
Received: from [156.154.16.129] (helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FEUbG-0006AJ-VQ
	for ldapext@ietf.org; Wed, 01 Mar 2006 11:54:54 -0500
Received: from 64-1-124-83.dsl.3u.net ([83.124.1.64]
	helo=srv1.int.stroeder.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1FETe2-0004GP-MH
	for ldapext@ietf.org; Wed, 01 Mar 2006 10:53:44 -0500
Received: from localhost (localhost [127.0.0.1])
	by srv1.int.stroeder.com (Postfix) with ESMTP id 6B2C3326D;
	Wed,  1 Mar 2006 16:53:40 +0100 (CET)
Received: from srv1.int.stroeder.com ([127.0.0.1])
	by localhost (srv1 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
	id 10512-04; Wed,  1 Mar 2006 16:53:33 +0100 (CET)
Received: from [10.1.1.5] (unknown [10.1.1.5])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client CN "Michael Stroeder",
	Issuer "Thawte Personal Freemail Issuing CA" (not verified))
	by srv1.int.stroeder.com (Postfix) with ESMTP id CB9ED316C;
	Wed,  1 Mar 2006 16:53:32 +0100 (CET)
Message-ID: <4405C37C.4060709@stroeder.com>
Date: Wed, 01 Mar 2006 16:53:32 +0100
From: =?ISO-8859-1?Q?Michael_Str=F6der?= <michael@stroeder.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050920
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: [ldapext] Fwd: I-D ACTION:draft-zeilenga-ldap-managedit-00.txt
References: <7.0.1.0.0.20060228132901.03d38568@OpenLDAP.org>
In-Reply-To: <7.0.1.0.0.20060228132901.03d38568@OpenLDAP.org>
X-Enigmail-Version: 0.93.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: amavisd-new at int.stroeder.com
X-Spam-Score: -2.6 (--)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: ldapext@ietf.org
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

Excerpt from section 3.6.:

  In absence
  of a document detailing that the NO-USER-MODIFICATION constraint on a
  particular operational attribute may be relaxed, implementors SHOULD
  assume relaxation of the constraint is not appropriate for that
  attribute.

This means a LDAP client cannot automatically determine which attributes
should be displayed as editable except a small known subset. Is that
really necessary?

I can understand your intention why you won't allow modification of
'structuralObjectClass' etc. But how about the server simply ignoring
them when sent in a modify request?

Ciao, Michael.

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Thu Mar 02 10:10:11 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FEpRR-0004GA-4G; Thu, 02 Mar 2006 10:10:09 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FEpRQ-0004G5-AZ
	for ldapext@ietf.org; Thu, 02 Mar 2006 10:10:08 -0500
Received: from moutng.kundenserver.de ([212.227.126.177])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FEpRO-0001mY-UL
	for ldapext@ietf.org; Thu, 02 Mar 2006 10:10:08 -0500
Received: from [84.188.239.152] (helo=[127.0.0.1])
	by mrelayeu.kundenserver.de (node=mrelayeu2) with ESMTP (Nemesis),
	id 0MKwtQ-1FEpRM3XJu-0007FT; Thu, 02 Mar 2006 16:10:05 +0100
Message-ID: <44070AD4.7010308@keutel.de>
Date: Thu, 02 Mar 2006 16:10:12 +0100
From: "Keutel, Jochen" <mlists@keutel.de>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: ldap@umich.edu, ldapext <ldapext@ietf.org>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: kundenserver.de abuse@kundenserver.de
	login:bd0f615417fb2508e1b23f8a312bf6cb
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Cc: 
Subject: [ldapext] certificateExactMatch and certificateMatch
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

Hello,
   both X.509 and draft-zeilenga-ldap-x509 define the matching rules
certificateExactMatch and certificateMatch. Questions:

1. Where is the string encoding for these matching rules defined?

I have seen that in OpenLDAP a string like

((userCertificate=1357$o=truetrust ltd,c=gb))

works for certificateExactMatch; also RFC3876 (matched values only)
uses this string representation. But I can't find a RFC/I-D which
defines this string format.

2. certificateMatch is defined in X.590 as

certificateMatch MATCHING-RULE ::= {
	SYNTAX	CertificateAssertion
	ID			id-mr-certificateMatch }
CertificateAssertion ::= SEQUENCE {
	serialNumber		[0] 	CertificateSerialNumber	OPTIONAL,
	issuer				[1] 	Name 			OPTIONAL,
	subjectKeyIdentifier	[2] 	SubjectKeyIdentifier		OPTIONAL,
	authorityKeyIdentifier	[3] 	AuthorityKeyIdentifier 	OPTIONAL,
	certificateValid		[4] 	Time			OPTIONAL,
	privateKeyValid		[5] 	GeneralizedTime		OPTIONAL,
	subjectPublicKeyAlgID	[6] 	OBJECT IDENTIFIER		OPTIONAL,
	keyUsage			[7] 	KeyUsage		OPTIONAL,
	subjectAltName		[8] 	AltNameType		OPTIONAL,
	policy				[9]	CertPolicySet		OPTIONAL,
	pathToName		[10] 	Name			OPTIONAL,
	subject				[11]	Name			OPTIONAL,
	nameConstraints		[12]	NameConstraintsSyntax	OPTIONAL
  }

. Is it possible to use this matching rule in LDAP? Is there any product
already supporting this matching rule?

E.g. it should be possible to search for certificates with
- keyUsage="keyEncipherment"
or
- subjectAltName "e-mail: aaa@bbb.cc"
, right?

How would be the string encoding for these 2 examples?

Regards,  Jochen.


_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Thu Mar 02 11:41:42 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FEqrz-0004du-Nu; Thu, 02 Mar 2006 11:41:39 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FEqrz-0004d3-1w
	for ldapext@ietf.org; Thu, 02 Mar 2006 11:41:39 -0500
Received: from boole.openldap.org ([204.152.186.50])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FEqry-00069y-Lp
	for ldapext@ietf.org; Thu, 02 Mar 2006 11:41:39 -0500
Received: from gyspy.OpenLDAP.org (24-205-218-53.dhcp.crcy.nv.charter.com
	[24.205.218.53] (may be forged)) (authenticated bits=0)
	by boole.openldap.org (8.13.3/8.13.3) with ESMTP id k22GfbD5021449
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 2 Mar 2006 16:41:37 GMT (envelope-from Kurt@OpenLDAP.org)
Message-Id: <7.0.1.0.0.20060302082326.0222ac00@OpenLDAP.org>
X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0
Date: Thu, 02 Mar 2006 08:41:01 -0800
To: "Keutel, Jochen" <mlists@keutel.de>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: [ldapext] certificateExactMatch and certificateMatch
In-Reply-To: <44070AD4.7010308@keutel.de>
References: <44070AD4.7010308@keutel.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Score: 0.1 (/)
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248
Cc: ldapext <ldapext@ietf.org>
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

[CC list trimmed to single list]

At 07:10 AM 3/2/2006, Keutel, Jochen wrote:
>Hello,
>  both X.509 and draft-zeilenga-ldap-x509 define the matching rules
>certificateExactMatch and certificateMatch. Questions:
>
>1. Where is the string encoding for these matching rules defined?

Yes, draft-zeilenga-ldap-x509 (an approved Proposed Standard, an
RFC-to-be) specifies the LDAP string encoding of these matching
rules to be the GSER [RFC3641] encoding of the value.

>I have seen that in OpenLDAP a string like
>((userCertificate=1357$o=truetrust ltd,c=gb))

The old format used here should be considered deprecated in favor
of the standard GSER string encoding.

>But I can't find a RFC/I-D which defines this string format.

As noted above, see draft-zeilenga-ldap-x509.  As an example,
  (userCertificate={ serialNumber 1357, issuer "o=truetrust ltd,c=gb" })


>2. certificateMatch is defined in X.590 as
>
>certificateMatch MATCHING-RULE ::= {
>        SYNTAX  CertificateAssertion
>        ID                      id-mr-certificateMatch }
>CertificateAssertion ::= SEQUENCE {
>        serialNumber            [0]     CertificateSerialNumber OPTIONAL,
>        issuer                          [1]     Name                    OPTIONAL,
>        subjectKeyIdentifier    [2]     SubjectKeyIdentifier            OPTIONAL,
>        authorityKeyIdentifier  [3]     AuthorityKeyIdentifier  OPTIONAL,
>        certificateValid                [4]     Time                    OPTIONAL,
>        privateKeyValid         [5]     GeneralizedTime         OPTIONAL,
>        subjectPublicKeyAlgID   [6]     OBJECT IDENTIFIER               OPTIONAL,
>        keyUsage                        [7]     KeyUsage                OPTIONAL,
>        subjectAltName          [8]     AltNameType             OPTIONAL,
>        policy                          [9]     CertPolicySet           OPTIONAL,
>        pathToName              [10]    Name                    OPTIONAL,
>        subject                         [11]    Name                    OPTIONAL,
>        nameConstraints         [12]    NameConstraintsSyntax   OPTIONAL
> }
>
>. Is it possible to use this matching rule in LDAP?

Yes, as specified in draft-zeilenga-ldap-x509.

>Is there any product already supporting this matching rule?

I believe this matching rule to be fully implemented as
specified in draft-zeilenga-ldap-x509 in at least one
implementation.

(I note that I am not counting OpenLDAP's implementation as it
is flawed in the current release, an issue I am currently working
on addressing.)

(I note I do not name implementations that I believe fully
implement this specification as I prefer not to make specific
claims regarding products of others.)


>E.g. it should be possible to search for certificates with
>- keyUsage="keyEncipherment"
>or
>- subjectAltName "e-mail: aaa@bbb.cc"
>, right?
>
>How would be the string encoding for these 2 examples?

As I don't trust my built-in GSER encoder to provide correct
encodings except for the most basic ASN.1 types, I'll leave
this to others.

Kurt 


_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Thu Mar 02 13:24:38 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FEsTb-000528-Ow; Thu, 02 Mar 2006 13:24:35 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FEsTa-000523-PE
	for ldapext@ietf.org; Thu, 02 Mar 2006 13:24:34 -0500
Received: from boole.openldap.org ([204.152.186.50])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FEsTZ-0001OG-Cm
	for ldapext@ietf.org; Thu, 02 Mar 2006 13:24:34 -0500
Received: from gyspy.OpenLDAP.org (24-205-218-53.dhcp.crcy.nv.charter.com
	[24.205.218.53] (may be forged)) (authenticated bits=0)
	by boole.openldap.org (8.13.3/8.13.3) with ESMTP id k22IOWcS027514
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 2 Mar 2006 18:24:32 GMT (envelope-from Kurt@OpenLDAP.org)
Message-Id: <7.0.1.0.0.20060302101200.041a4680@OpenLDAP.org>
X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0
Date: Thu, 02 Mar 2006 10:23:55 -0800
To: John McMeeking <jmcmeek@us.ibm.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: [ldapext] Fwd: I-D
  ACTION:draft-zeilenga-ldap-managedit-00.txt
In-Reply-To: <OFB5A0E890.88D5476C-ON86257124.00486BD7-86257124.004CE95A@
	us.ibm.com>
References: <7.0.1.0.0.20060228132901.03d38568@OpenLDAP.org>
	<OFB5A0E890.88D5476C-ON86257124.00486BD7-86257124.004CE95A@us.ibm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Score: 0.1 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: ldapext@ietf.org
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

At 06:00 AM 3/1/2006, John McMeeking wrote:

>I would like to see a name for the control that is not so close to the existing ManageDsaIT control.  I picture someone using the wrong control because of the similarity in names.  Maybe something along the lines of "repair DIT" or "allow exceptions"? 

Noted.  How about the "relax" control?

>I have occasionally found the need for such a mechanism. 
>
>I've always been a little uneasy about making it too easy to use for fear that an administrator would start using such a control for one purpose and either use it where it shouldn't have been used -- like inadvertantly updating an entry on a read-only replica because he misdiagnosed a problem, or using it to fix one problem and because of the controls presence also be allowed to do something else unintended.  Or worse yet, just start using the control out of bad habit. 
>
>I'm trying to think of something that makes the control perhaps a little less dangerous without making it impossible to use.  In some respects, maybe what I really want is an interactive "are you sure you want to do this" capability; of course those always come with a "yes to all" option, so maybe I'm just unduly paranoid.  Maybe there could be a family of controls - one control for each kind of exceptional action - or a control value indicating the kind of change intended. 

I have considered whether the control should or should not provide
fine grained control over the relaxation of various schema restrictions
and model constraints.   I concluded it would be too hard to specify,
implement, to use (from a client perspective), to manage (from a
server policy perspective).   I concluded it was much easier to
say the control "relaxed" temporarily various restrictions/constraints,
subject to administrative and other controls.

In our early implementation, the client has to have
context-specific authorization to use this control.
That is, they need to have "manage" rights on the
object (or particular attributes of the objects)
to use this control.  It's homed that the
administrator will not grant "manage" rights to all
those who have "write" rights.

Kurt 


_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Thu Mar 02 13:45:44 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FEso4-0003Y9-04; Thu, 02 Mar 2006 13:45:44 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FEso3-0003Y4-8b
	for ldapext@ietf.org; Thu, 02 Mar 2006 13:45:43 -0500
Received: from boole.openldap.org ([204.152.186.50])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FEso2-0002Dn-SC
	for ldapext@ietf.org; Thu, 02 Mar 2006 13:45:43 -0500
Received: from gyspy.OpenLDAP.org (24-205-218-53.dhcp.crcy.nv.charter.com
	[24.205.218.53] (may be forged)) (authenticated bits=0)
	by boole.openldap.org (8.13.3/8.13.3) with ESMTP id k22Ijcjf028655
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 2 Mar 2006 18:45:38 GMT (envelope-from Kurt@OpenLDAP.org)
Message-Id: <7.0.1.0.0.20060302102410.041e2868@OpenLDAP.org>
X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0
Date: Thu, 02 Mar 2006 10:45:01 -0800
To: Michael Ströder <michael@stroeder.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: [ldapext] Fwd: I-D
  ACTION:draft-zeilenga-ldap-managedit-00.txt
In-Reply-To: <4405C37C.4060709@stroeder.com>
References: <7.0.1.0.0.20060228132901.03d38568@OpenLDAP.org>
	<4405C37C.4060709@stroeder.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by boole.openldap.org id
	k22Ijcjf028655
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Cc: ldapext@ietf.org
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

At 07:53 AM 3/1/2006, Michael Str=F6der wrote:
>Excerpt from section 3.6.:
>
>  In absence
>  of a document detailing that the NO-USER-MODIFICATION constraint on a
>  particular operational attribute may be relaxed, implementors SHOULD
>  assume relaxation of the constraint is not appropriate for that
>  attribute.
>
>This means a LDAP client cannot automatically determine which attributes
>should be displayed as editable except a small known subset.

The specification does not provide any facility for determining
whether any particular NO-USER-MODIFICATION attribute can
be modified through use of this control.  As I intend the
control to only be used in limited cases, mainly when purposely
selected by the directory administrator to undertake a task
he/she knows requires it (and is allowed by it), I saw no
need to detail which particular NO-USER-MODIFICATION constraints
can be relaxed.

>Is that really necessary?

Even without this statement, I note that implementations are
not to relax the NO-USER-MODIFICATION in cases where doing
so would be problematic.  For instance, a server should
prevent modification of modifyTimestamp is doing so would
hose directory services, such as replication or client
synchronization services.   This implies not only a need for
server implementation-specific constraints upon use of
this control, but local policy constraints.

>I can understand your intention why you won't allow modification of
>'structuralObjectClass' etc. But how about the server simply ignoring
>them when sent in a modify request?

Because then the client has no clue what modification, if
any, took place.

Of course, a client could possibly provide a "permissive
modify" control as well...



>Ciao, Michael.
>
>_______________________________________________
>Ldapext mailing list
>Ldapext@ietf.org
>https://www1.ietf.org/mailman/listinfo/ldapext


_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Thu Mar 02 14:15:32 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FEtGt-0006ik-Tu; Thu, 02 Mar 2006 14:15:31 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FEtGs-0006ic-Fk
	for ldapext@ietf.org; Thu, 02 Mar 2006 14:15:30 -0500
Received: from e3.ny.us.ibm.com ([32.97.182.143])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FEtGr-0003Ny-5Q
	for ldapext@ietf.org; Thu, 02 Mar 2006 14:15:30 -0500
Received: from d01relay04.pok.ibm.com (d01relay04.pok.ibm.com [9.56.227.236])
	by e3.ny.us.ibm.com (8.12.11/8.12.11) with ESMTP id k22JFSLO029270
	for <ldapext@ietf.org>; Thu, 2 Mar 2006 14:15:28 -0500
Received: from d01av03.pok.ibm.com (d01av03.pok.ibm.com [9.56.224.217])
	by d01relay04.pok.ibm.com (8.12.10/NCO/VER6.8) with ESMTP id
	k22JFSnF218476 for <ldapext@ietf.org>; Thu, 2 Mar 2006 14:15:28 -0500
Received: from d01av03.pok.ibm.com (loopback [127.0.0.1])
	by d01av03.pok.ibm.com (8.12.11/8.13.3) with ESMTP id k22JFSwe005481
	for <ldapext@ietf.org>; Thu, 2 Mar 2006 14:15:28 -0500
Received: from d27ml001.rchland.ibm.com (d27ml001.rchland.ibm.com
	[9.10.229.77])
	by d01av03.pok.ibm.com (8.12.11/8.12.11) with ESMTP id k22JFSkD005474
	for <ldapext@ietf.org>; Thu, 2 Mar 2006 14:15:28 -0500
In-Reply-To: <7.0.1.0.0.20060302101200.041a4680@OpenLDAP.org>
To: ldapext@ietf.org
Subject: Re: [ldapext] Fwd: I-D  ACTION:draft-zeilenga-ldap-managedit-00.txt
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 7.0 HF85 November 04, 2005
From: John McMeeking <jmcmeek@us.ibm.com>
Message-ID: <OF1F706F8E.83B5208F-ON86257125.0068B565-86257125.0069C8C3@us.ibm.com>
Date: Thu, 2 Mar 2006 13:15:28 -0600
X-MIMETrack: Serialize by Router on d27ml001/27/M/IBM(Release 7.0.1|January 17,
	2006) at 03/02/2006 01:15:27 PM,
	Serialize complete at 03/02/2006 01:15:27 PM
X-Spam-Score: 1.3 (+)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0815858125=="
Errors-To: ldapext-bounces@ietf.org

--===============0815858125==
Content-Type: text/html; charset="US-ASCII"


<br><tt><font size=2>&quot;Kurt D. Zeilenga&quot; &lt;Kurt@OpenLDAP.org&gt;
wrote on 03/02/2006 12:23:55 PM:<br>
<br>
&gt; At 06:00 AM 3/1/2006, John McMeeking wrote:<br>
&gt; <br>
&gt; &gt;I would like to see a name for the control that is not so close
to <br>
&gt; the existing ManageDsaIT control. &nbsp;I picture someone using the
wrong<br>
&gt; control because of the similarity in names. &nbsp;Maybe something
along <br>
&gt; the lines of &quot;repair DIT&quot; or &quot;allow exceptions&quot;?
<br>
&gt; <br>
&gt; Noted. &nbsp;How about the &quot;relax&quot; control?<br>
</font></tt>
<br><tt><font size=2>That would be better.</font></tt>
<br>
<br><tt><font size=2>&gt; <br>
&gt; Kurt <br>
&gt; <br>
&gt; <br>
&gt; _______________________________________________<br>
&gt; Ldapext mailing list<br>
&gt; Ldapext@ietf.org<br>
&gt; https://www1.ietf.org/mailman/listinfo/ldapext<br>
</font></tt>
<br>
<br><tt><font size=2>John McMeeking</font></tt>


--===============0815858125==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext

--===============0815858125==--



From ldapext-bounces@ietf.org Thu Mar 02 18:18:40 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FEx4B-0003Lj-A5; Thu, 02 Mar 2006 18:18:39 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FEx49-0003L0-NN
	for ldapext@ietf.org; Thu, 02 Mar 2006 18:18:37 -0500
Received: from eagle.unknowndns.net ([221.133.206.175])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FEx48-0003CV-Uc
	for ldapext@ietf.org; Thu, 02 Mar 2006 18:18:37 -0500
Received: from cust1793.vic01.dataco.com.au ([202.63.57.1]
	helo=[192.168.39.32]) by eagle.unknowndns.net with esmtpa (Exim 4.52)
	id 1FEx46-0001sl-6x; Fri, 03 Mar 2006 09:18:34 +1000
Message-ID: <44077D4A.30103@eb2bcom.com>
Date: Fri, 03 Mar 2006 10:18:34 +1100
From: Mark Ennis <mark.ennis@eb2bcom.com>
User-Agent: Mozilla Thunderbird 1.0.7-1.1.fc4 (X11/20050929)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: [ldapext] Fwd: I-D ACTION:draft-zeilenga-ldap-managedit-00.txt
References: <7.0.1.0.0.20060228132901.03d38568@OpenLDAP.org>
In-Reply-To: <7.0.1.0.0.20060228132901.03d38568@OpenLDAP.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - eagle.unknowndns.net
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12]
X-AntiAbuse: Sender Address Domain - eb2bcom.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 944ecb6e61f753561f559a497458fb4f
Cc: ldapext@ietf.org
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

Kurt,

We implemented something very similar to this recently, which we called 
a schema checking control. The only significant difference is that we 
introduced an extra level of control.

That is, without the LDAP control, we carry out full schema checking,
with the control, we have three possible settings:
i) no schema checking.
ii) do all schema checking except the NO USER MODIFICATION property of
the attribute type description.
iii) full schema checking.

We use option ii) for importing data into the directory. It allows
createTimestamp, etc. to be specified in the dump, but otherwise checks
the schema is correct and rebuilds structuralObjectClass and
governingStructureRule.

- Mark.

Kurt D. Zeilenga wrote:
> Enjoy!  -- Kurt
> 
> 
>>To: i-d-announce@ietf.org
>>Cc: 
>>From: Internet-Drafts@ietf.org
>>Date: Tue, 28 Feb 2006 15:50:01 -0500
>>Subject: I-D ACTION:draft-zeilenga-ldap-managedit-00.txt 
>>Reply-To: internet-drafts@ietf.org
>>
>>A New Internet-Draft is available from the on-line Internet-Drafts directories.
>>
>>
>>       Title           : The LDAP Manage Directory Information Tree Control
>>       Author(s)       : K. Zeilenga
>>       Filename        : draft-zeilenga-ldap-managedit-00.txt
>>       Pages           : 12
>>       Date            : 2006-2-28
>>       
>>This document defines the Lightweight Directory Access Protocol (LDAP)
>>Manage Directory Information Tree (DIT) Control which allows a
>>directory user agent (a client) to request the directory service
>>temporarily relax enforcement of constraints of the X.500 models.
>>
>>
>>A URL for this Internet-Draft is:
>>http://www.ietf.org/internet-drafts/draft-zeilenga-ldap-managedit-00.txt
>>
>>To remove yourself from the I-D Announcement list, send a message to 
>>i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
>>You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
>>to change your subscription settings.
>>
>>
>>Internet-Drafts are also available by anonymous FTP. Login with the username
>>"anonymous" and a password of your e-mail address. After logging in,
>>type "cd internet-drafts" and then
>>       "get draft-zeilenga-ldap-managedit-00.txt".
>>
>>A list of Internet-Drafts directories can be found in
>>http://www.ietf.org/shadow.html 
>>or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>
>>
>>Internet-Drafts can also be obtained by e-mail.
>>
>>Send a message to:
>>       mailserv@ietf.org.
>>In the body type:
>>       "FILE /internet-drafts/draft-zeilenga-ldap-managedit-00.txt".
>>       
>>NOTE:   The mail server at ietf.org can return the document in
>>       MIME-encoded form by using the "mpack" utility.  To use this
>>       feature, insert the command "ENCODING mime" before the "FILE"
>>       command.  To decode the response(s), you will need "munpack" or
>>       a MIME-compliant mail reader.  Different MIME-compliant mail readers
>>       exhibit different behavior, especially when dealing with
>>       "multipart" MIME messages (i.e. documents which have been split
>>       up into multiple messages), so check your local documentation on
>>       how to manipulate these messages.
>>               
>>               
>>Below is the data which will enable a MIME compliant mail reader
>>implementation to automatically retrieve the ASCII version of the
>>Internet-Draft.
>>
>>Content-Type: text/plain
>>Content-ID: <2006-2-28130944.I-D@ietf.org>
>>
>>ENCODING mime
>>FILE /internet-drafts/draft-zeilenga-ldap-managedit-00.txt
>>
>>
>><ftp://ftp.ietf.org/internet-drafts/draft-zeilenga-ldap-managedit-00.txt>
>>_______________________________________________
>>I-D-Announce mailing list
>>I-D-Announce@ietf.org
>>https://www1.ietf.org/mailman/listinfo/i-d-announce
> 
> 
> 
> _______________________________________________
> Ldapext mailing list
> Ldapext@ietf.org
> https://www1.ietf.org/mailman/listinfo/ldapext
> 

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Thu Mar 02 20:27:37 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FEz4x-0006Wh-SD; Thu, 02 Mar 2006 20:27:35 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FEz4v-0006Uk-PD
	for ldapext@ietf.org; Thu, 02 Mar 2006 20:27:33 -0500
Received: from eagle.unknowndns.net ([221.133.206.175])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FEz4u-0003tD-MN
	for ldapext@ietf.org; Thu, 02 Mar 2006 20:27:33 -0500
Received: from [203.206.165.210] (helo=[192.168.1.156])
	by eagle.unknowndns.net with esmtpa (Exim 4.52)
	id 1FEz4h-00076H-3s; Fri, 03 Mar 2006 11:27:19 +1000
Message-ID: <44079B74.80200@eb2bcom.com>
Date: Fri, 03 Mar 2006 12:27:16 +1100
From: Steven Legg <steven.legg@eb2bcom.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.6) Gecko/20050319
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Keutel, Jochen" <mlists@keutel.de>
Subject: Re: [ldapext] certificateExactMatch and certificateMatch
References: <44070AD4.7010308@keutel.de>
	<7.0.1.0.0.20060302082326.0222ac00@OpenLDAP.org>
In-Reply-To: <7.0.1.0.0.20060302082326.0222ac00@OpenLDAP.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - eagle.unknowndns.net
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12]
X-AntiAbuse: Sender Address Domain - eb2bcom.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 36b1f8810cb91289d885dc8ab4fc8172
Cc: ldapext <ldapext@ietf.org>, "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org


Jochen,

Kurt D. Zeilenga wrote:
> [CC list trimmed to single list]
> 
> At 07:10 AM 3/2/2006, Keutel, Jochen wrote:
> 
>>Hello,
>> both X.509 and draft-zeilenga-ldap-x509 define the matching rules
>>certificateExactMatch and certificateMatch. Questions:
>>
>>1. Where is the string encoding for these matching rules defined?
> 
> 
> Yes, draft-zeilenga-ldap-x509 (an approved Proposed Standard, an
> RFC-to-be) specifies the LDAP string encoding of these matching
> rules to be the GSER [RFC3641] encoding of the value.
> 
> 
>>I have seen that in OpenLDAP a string like
>>((userCertificate=1357$o=truetrust ltd,c=gb))
> 
> 
> The old format used here should be considered deprecated in favor
> of the standard GSER string encoding.
> 
> 
>>But I can't find a RFC/I-D which defines this string format.
> 
> 
> As noted above, see draft-zeilenga-ldap-x509.  As an example,
>   (userCertificate={ serialNumber 1357, issuer "o=truetrust ltd,c=gb" })
> 
> 
> 
>>2. certificateMatch is defined in X.590 as
>>
>>certificateMatch MATCHING-RULE ::= {
>>       SYNTAX  CertificateAssertion
>>       ID                      id-mr-certificateMatch }
>>CertificateAssertion ::= SEQUENCE {
>>       serialNumber            [0]     CertificateSerialNumber OPTIONAL,
>>       issuer                          [1]     Name                    OPTIONAL,
>>       subjectKeyIdentifier    [2]     SubjectKeyIdentifier            OPTIONAL,
>>       authorityKeyIdentifier  [3]     AuthorityKeyIdentifier  OPTIONAL,
>>       certificateValid                [4]     Time                    OPTIONAL,
>>       privateKeyValid         [5]     GeneralizedTime         OPTIONAL,
>>       subjectPublicKeyAlgID   [6]     OBJECT IDENTIFIER               OPTIONAL,
>>       keyUsage                        [7]     KeyUsage                OPTIONAL,
>>       subjectAltName          [8]     AltNameType             OPTIONAL,
>>       policy                          [9]     CertPolicySet           OPTIONAL,
>>       pathToName              [10]    Name                    OPTIONAL,
>>       subject                         [11]    Name                    OPTIONAL,
>>       nameConstraints         [12]    NameConstraintsSyntax   OPTIONAL
>>}
>>
>>. Is it possible to use this matching rule in LDAP?
> 
> 
> Yes, as specified in draft-zeilenga-ldap-x509.
> 
> 
>>Is there any product already supporting this matching rule?
> 
> 
> I believe this matching rule to be fully implemented as
> specified in draft-zeilenga-ldap-x509 in at least one
> implementation.
> 
> (I note that I am not counting OpenLDAP's implementation as it
> is flawed in the current release, an issue I am currently working
> on addressing.)
> 
> (I note I do not name implementations that I believe fully
> implement this specification as I prefer not to make specific
> claims regarding products of others.)

But those others can make claims about their own products :-).
eB2Bcom's directory server supports the certificateMatch matching rule.
In our current release the certificateMatch matching rule expects
the LDAP assertion value to be BER encoded by default, but it is possible
to use the GSER encoding, as specified in draft-zeilenga-ldap-x509, by
attaching ";transfer-gser" to the attribute type in the extensibleMatch
filter item. Now that draft-zeilenga-ldap-x509 is approved we will be
changing the default encoding over to GSER in the next release.

> 
> 
> 
>>E.g. it should be possible to search for certificates with
>>- keyUsage="keyEncipherment"
>>or
>>- subjectAltName "e-mail: aaa@bbb.cc"
>>, right?
>>
>>How would be the string encoding for these 2 examples?

In the first case the LDAP assertion value would be:

    { keyUsage { keyEncipherment } }

Note that the subjectAltName field of CertificateAssertion only allows
searching for subject alt names of a particular kind. To find all
certificates with email addresses as subject alt names the assertion
value would be:

    { subjectAltName builtinNameForm:rfc822Name }

You can't use certificateMatch to search for particular subjectAltName
email addresses, but it is possible to use component matching (RFC 3687) to
do this. The LDAP extensibleMatch filter item would look something like this
(minus the line breaks):

    (userCertificate:componentFilterMatch:=item:{
        component "toBeSigned.extensions.*.extnValue.content.(2.5.29.17).*.rfc822Name",
        rule caseIgnoreIA5Match, value "aaa@bbb.cc" })

Our directory server supports this as well.

Regards,
Steven

> 
> 
> As I don't trust my built-in GSER encoder to provide correct
> encodings except for the most basic ASN.1 types, I'll leave
> this to others.
> 
> Kurt 
> 
> 
> _______________________________________________
> Ldapext mailing list
> Ldapext@ietf.org
> https://www1.ietf.org/mailman/listinfo/ldapext
> 
> 
> 

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Fri Mar 03 02:53:58 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FF56l-0005kD-V7; Fri, 03 Mar 2006 02:53:51 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FF56k-0005ij-Mf
	for ldapext@ietf.org; Fri, 03 Mar 2006 02:53:50 -0500
Received: from 198-18-124-83.dsl.3u.net ([83.124.18.198]
	helo=srv1.int.stroeder.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FF56g-0000yP-74
	for ldapext@ietf.org; Fri, 03 Mar 2006 02:53:50 -0500
Received: from localhost (localhost [127.0.0.1])
	by srv1.int.stroeder.com (Postfix) with ESMTP id 372DF33E4;
	Fri,  3 Mar 2006 08:53:44 +0100 (CET)
Received: from srv1.int.stroeder.com ([127.0.0.1])
	by localhost (srv1 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
	id 24771-08; Fri,  3 Mar 2006 08:53:35 +0100 (CET)
Received: from mstroeder.homeip.net (localhost [127.0.0.1])
	by srv1.int.stroeder.com (Postfix) with SMTP id 94AF433B1;
	Fri,  3 Mar 2006 08:53:34 +0100 (CET)
Message-ID: <8b298a4525adc5787d89f441b87fb51a@stroeder.com>
Date: Fri,  3 Mar 2006 08:53:34 +0100
From: =?UTF-8?B?Ik1pY2hhZWwgU3Ryw7ZkZXIi?= <michael@stroeder.com>
Subject: Re: [ldapext] Fwd: I-D ACTION:draft-zeilenga-ldap-managedit-00.txt
To: " Kurt D. Zeilenga " <Kurt@OpenLDAP.org>
In-Reply-To: <7.0.1.0.0.20060302101200.041a4680@OpenLDAP.org>
References: <7.0.1.0.0.20060228132901.03d38568@OpenLDAP.org>
	<OFB5A0E890.88D5476C-ON86257124.00486BD7-86257124.004CE95A@us.ibm.com>
	<7.0.1.0.0.20060302101200.041a4680@OpenLDAP.org>
X-Mailer: hastymail 1.5
x-priority: 3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Virus-Scanned: amavisd-new at int.stroeder.com
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Cc: jmcmeek@us.ibm.com, ldapext@ietf.org
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: michael@stroeder.com
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

On 7:23:55 pm 2006-03-02 "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> wrote:
> At 06:00 AM 3/1/2006, John McMeeking wrote:
>
> > I would like to see a name for the control that is not so close to
> the existing ManageDsaIT control.  I picture someone using the wrong
> control because of the similarity in names.  Maybe something along the
> lines of "repair DIT" or "allow exceptions"?
>
> Noted.  How about the "relax" control?

I'd name it "relax DIT constrains" control.

Ciao, Michael.


_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Tue Mar 07 19:43:22 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FGmlq-0004Z3-SL; Tue, 07 Mar 2006 19:43:18 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FGmlq-0004Yt-46
	for ldapext@ietf.org; Tue, 07 Mar 2006 19:43:18 -0500
Received: from boole.openldap.org ([204.152.186.50])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FGmlp-00052b-ME
	for ldapext@ietf.org; Tue, 07 Mar 2006 19:43:18 -0500
Received: from gyspy.OpenLDAP.org (24-205-218-53.dhcp.crcy.nv.charter.com
	[24.205.218.53] (may be forged)) (authenticated bits=0)
	by boole.openldap.org (8.13.3/8.13.3) with ESMTP id k280hGR7070931
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <ldapext@ietf.org>; Wed, 8 Mar 2006 00:43:16 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <7.0.1.0.0.20060307163521.03e1f7a8@OpenLDAP.org>
X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0
Date: Tue, 07 Mar 2006 16:42:57 -0800
To: ldapext@ietf.org
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Score: 0.1 (/)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2
Subject: [ldapext] Fwd: I-D ACTION:draft-zeilenga-ldap-txn-07.txt 
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

In this revision of this draft, I have reworked the extension
to directly make use of LDAP extended operation/control
extension mechanisms instead of the LDAP "grouping of related
operations" proposed extension mechanism.  I do not intend
to pursue publication of the LDAP "grouping of related
operations" proposed extension mechanism.

I have yet to detail how LDAP Transactions may (or may not)
be used with various extensions to LDAP update messages,
in particular, the LDAP assertion and the LDAP pre/post
read controls.

My present plans are to progress this I-D on the Standards
Track after I deal with above issue and complete an early
implementation of the specification.

Kurt

>To: i-d-announce@ietf.org
>Cc: 
>From: Internet-Drafts@ietf.org
>Date: Tue, 07 Mar 2006 15:50:03 -0500
>Subject: I-D ACTION:draft-zeilenga-ldap-txn-07.txt 
>Reply-To: internet-drafts@ietf.org
>
>A New Internet-Draft is available from the on-line Internet-Drafts directories.
>
>
>        Title           : LDAP Transactions
>        Author(s)       : K. Zeilenga
>        Filename        : draft-zeilenga-ldap-txn-07.txt
>        Pages           : 9
>        Date            : 2006-3-7
>        
>Lightweight Directory Access Protocol (LDAP) update operations, such
>  as Add, Delete, and Modify operations, have atomic, consistency,
>  isolation, durability (ACID) properties.  Each of these update
>  operations act upon an entry.  However, It is often desirable to
>  update two or more entries in a single unit of interaction, a
>  transaction.  Transactions are necessary to support a number of
>  applications including resource provisioning and information
>  replication.  This document defines an LDAP extension to support
>  transactions.
>
>A URL for this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-zeilenga-ldap-txn-07.txt
>
>To remove yourself from the I-D Announcement list, send a message to 
>i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
>You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
>to change your subscription settings.
>
>
>Internet-Drafts are also available by anonymous FTP. Login with the username
>"anonymous" and a password of your e-mail address. After logging in,
>type "cd internet-drafts" and then
>        "get draft-zeilenga-ldap-txn-07.txt".
>
>A list of Internet-Drafts directories can be found in
>http://www.ietf.org/shadow.html 
>or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>
>Internet-Drafts can also be obtained by e-mail.
>
>Send a message to:
>        mailserv@ietf.org.
>In the body type:
>        "FILE /internet-drafts/draft-zeilenga-ldap-txn-07.txt".
>        
>NOTE:   The mail server at ietf.org can return the document in
>        MIME-encoded form by using the "mpack" utility.  To use this
>        feature, insert the command "ENCODING mime" before the "FILE"
>        command.  To decode the response(s), you will need "munpack" or
>        a MIME-compliant mail reader.  Different MIME-compliant mail readers
>        exhibit different behavior, especially when dealing with
>        "multipart" MIME messages (i.e. documents which have been split
>        up into multiple messages), so check your local documentation on
>        how to manipulate these messages.
>                
>                
>Below is the data which will enable a MIME compliant mail reader
>implementation to automatically retrieve the ASCII version of the
>Internet-Draft.
>
>Content-Type: text/plain
>Content-ID: <2006-3-7134158.I-D@ietf.org>
>
>ENCODING mime
>FILE /internet-drafts/draft-zeilenga-ldap-txn-07.txt
>
>
><ftp://ftp.ietf.org/internet-drafts/draft-zeilenga-ldap-txn-07.txt>
>_______________________________________________
>I-D-Announce mailing list
>I-D-Announce@ietf.org
>https://www1.ietf.org/mailman/listinfo/i-d-announce


_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Thu Mar 09 14:06:25 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FHQSu-0002FJ-BY; Thu, 09 Mar 2006 14:06:24 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FHQSt-0002FE-Iz
	for ldapext@ietf.org; Thu, 09 Mar 2006 14:06:23 -0500
Received: from boole.openldap.org ([204.152.186.50])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FHQSq-0004BE-7E
	for ldapext@ietf.org; Thu, 09 Mar 2006 14:06:23 -0500
Received: from gypsy.OpenLDAP.org (24-205-218-53.dhcp.crcy.nv.charter.com
	[24.205.218.53] (may be forged)) (authenticated bits=0)
	by boole.openldap.org (8.13.3/8.13.3) with ESMTP id k29J6IW1081362
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <ldapext@ietf.org>; Thu, 9 Mar 2006 19:06:19 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <7.0.1.0.0.20060308105910.03211190@OpenLDAP.org>
X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0
Date: Wed, 08 Mar 2006 11:05:52 -0800
To: ldapext@ietf.org
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Score: 0.4 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Subject: [ldapext] dirdir session
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

At present, it seems that many of the LDAP regulars,
especially our normal base of authors/editors,
will not be able to attend this session in person.
Hence, I have decided to cancel the session.  In its
place, I suggest we can arrange a jabber session
and/or telechat after IETF#65.  We will, of course,
have the usual rounds of ad hoc discussion of LDAP
works in progress.

Regards, Kurt


_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Mon Mar 20 19:47:49 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FLV2J-0001IR-G7; Mon, 20 Mar 2006 19:47:47 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FLV2H-0001IM-L6
	for ldapext@ietf.org; Mon, 20 Mar 2006 19:47:45 -0500
Received: from boole.openldap.org ([204.152.186.50])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLV2G-0004w1-9g
	for ldapext@ietf.org; Mon, 20 Mar 2006 19:47:45 -0500
Received: from gypsy.OpenLDAP.org (DHCP-Wireless-133-173.ietf65.org
	[130.129.133.173]) (authenticated bits=0)
	by boole.openldap.org (8.13.3/8.13.3) with ESMTP id k2L0lf7f059288
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <ldapext@ietf.org>; Tue, 21 Mar 2006 00:47:42 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <7.0.1.0.0.20060320183713.021c6558@OpenLDAP.org>
X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0
Date: Mon, 20 Mar 2006 18:47:36 -0600
To: ldapext@ietf.org
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 0f1ff0b0158b41ac6b9548d0972cdd31
Subject: [ldapext] dirdir bar session
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

Met at the tower bar at 10pm.


_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Sun Mar 26 20:23:21 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FNgRz-0002NX-7e; Sun, 26 Mar 2006 20:23:19 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FNgRy-0002LU-CR
	for ldapext@ietf.org; Sun, 26 Mar 2006 20:23:18 -0500
Received: from web38904.mail.mud.yahoo.com ([209.191.125.110])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1FNgRy-0002xD-1H
	for ldapext@ietf.org; Sun, 26 Mar 2006 20:23:18 -0500
Received: (qmail 28215 invoked by uid 60001); 27 Mar 2006 01:23:17 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding;
	b=U29yXgLYmFsbS2vlHM72dnvIvysG3mEnKHUkEgXRROcuZEhlUobHSTWCM9X+BaBJIyMX6zKELQYq5mMfDV/8+QoeHVi1pdI4PGaKxPfJA/teqXQJTTpxcJtrkdjH0LAJ9lSFCAxKFi3x3aaAeytUNYSEpQdBbaD0bPB73i7DtdA=
	; 
Message-ID: <20060327012317.28213.qmail@web38904.mail.mud.yahoo.com>
Received: from [202.90.158.202] by web38904.mail.mud.yahoo.com via HTTP;
	Sun, 26 Mar 2006 17:23:17 PST
Date: Sun, 26 Mar 2006 17:23:17 -0800 (PST)
From: jay alvarez <ldapb0y@yahoo.com>
To: ldapext@ietf.org
MIME-Version: 1.0
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Subject: [ldapext] ppolicy questions
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0220347014=="
Errors-To: ldapext-bounces@ietf.org

--===============0220347014==
Content-Type: multipart/alternative; boundary="0-1250324468-1143422597=:26545"
Content-Transfer-Encoding: 8bit

--0-1250324468-1143422597=:26545
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

   Good day,
  
  I have some questions regarding draft-behera-ldap-password-policy-08.txt.
  
  1. Do you know if it has been standardized or updated yet?
  2.In pwdCheckQuality, it says  it is still in TODO list.. Do you know how to enforce the minimum included characters like it must have Upper, lower, number, special characters without administrator intervention? Sure, I can use some random password generation tools to enforce these requirements but I'm thinking a lot of negative implications..
  
  3. how does expiration warning shown to the user?? Let's say, I would do an ldapsearch in the commandline and do a simple bind... it didn't tell me if my password is about to expire even if I run it in verbose mode..
  
  4. What if in pwdMustChange, the user did not change his password after initial bind or reset by administrator?? What will happen?? The attribute explanation doesn't say anything about this....
  
  5. How to send old password when changing to  a new password(pwdSafeModify)?? 
  I've looked into ldapmodify and found nothing about this.
  My file looks like this:
  
  dn: uid=jayson,ou=people,o=example,dc=com
  changetype: modify
  replace: userPassword
  userPassword: {SSHA}g/pfweYQQRtYFxVGwhn8xnCCEcY0rDTDQ
  
  On ldapmodify operation, I got this error:
  ldap_modify: Insufficient access (50)
          additional info: Must supply old password to be changed as well as new one
  
  
  
  That's all for now, thanks!
  -jay
__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
--0-1250324468-1143422597=:26545
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

   Good day,<br>  <br>  I have some questions regarding draft-behera-ldap-password-policy-08.txt.<br>  <br>  1. Do you know if it has been standardized or updated yet?<br>  2.In pwdCheckQuality, it says&nbsp; it is still in TODO list.. Do you know how to enforce the minimum included characters like it must have Upper, lower, number, special characters without administrator intervention? Sure, I can use some random password generation tools to enforce these requirements but I'm thinking a lot of negative implications..<br>  <br>  3. how does expiration warning shown to the user?? Let's say, I would do an ldapsearch in the commandline and do a simple bind... it didn't tell me if my password is about to expire even if I run it in verbose mode..<br>  <br>  4. What if in pwdMustChange, the user did not change his password after initial bind or reset by administrator?? What will happen?? The attribute explanation doesn't say anything about this....<br>  <br>  5. How to send old password
 when changing to  a new password(pwdSafeModify)?? <br>  I've looked into ldapmodify and found nothing about this.<br>  My file looks like this:<br>  <br>  dn: uid=jayson,ou=people,o=example,dc=com<br>  changetype: modify<br>  replace: userPassword<br>  userPassword: {SSHA}g/pfweYQQRtYFxVGwhn8xnCCEcY0rDTDQ<br>  <br>  On ldapmodify operation, I got this error:<br>  ldap_modify: Insufficient access (50)<br>  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; additional info: Must supply old password to be changed as well as new one<br>  <br>  <br>  <br>  That's all for now, thanks!<br>  -jay<p>__________________________________________________<br>Do You Yahoo!?<br>Tired of spam?  Yahoo! Mail has the best spam protection around <br>http://mail.yahoo.com 
--0-1250324468-1143422597=:26545--


--===============0220347014==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext

--===============0220347014==--




From ldapext-bounces@ietf.org Sun Mar 26 20:41:45 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FNgjp-0003nx-6r; Sun, 26 Mar 2006 20:41:45 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FNgjo-0003nq-Pe
	for ldapext@ietf.org; Sun, 26 Mar 2006 20:41:44 -0500
Received: from brmea-mail-2.sun.com ([192.18.98.43])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FNgjn-0003Cw-Bu
	for ldapext@ietf.org; Sun, 26 Mar 2006 20:41:44 -0500
Received: from phys-gadget-1 ([129.156.85.171])
	by brmea-mail-2.sun.com (8.12.10/8.12.9) with ESMTP id k2R1fg8u005319
	for <ldapext@ietf.org>; Sun, 26 Mar 2006 18:41:42 -0700 (MST)
Received: from conversion-daemon.gadget-mail1.uk.sun.com by
	gadget-mail1.uk.sun.com
	(iPlanet Messaging Server 5.2 HotFix 1.24 (built Dec 19 2003))
	id <0IWR00A01JAD46@gadget-mail1.uk.sun.com>
	(original mail from Ludovic.Poitou@Sun.COM) for ldapext@ietf.org; Mon,
	27 Mar 2006 02:41:42 +0100 (BST)
Received: from [129.150.33.71]
	(vpn-129-150-33-71.Central.Sun.COM [129.150.33.71]) by
	gadget-mail1.uk.sun.com
	(iPlanet Messaging Server 5.2 HotFix 1.24 (built Dec 19 2003))
	with ESMTPA id <0IWR00CCWJDGUZ@gadget-mail1.uk.sun.com>; Mon,
	27 Mar 2006 02:41:42 +0100 (BST)
Date: Mon, 27 Mar 2006 03:43:01 +0200
From: Ludovic Poitou <Ludovic.Poitou@Sun.COM>
Subject: Re: [ldapext] ppolicy questions
In-reply-to: <20060327012317.28213.qmail@web38904.mail.mud.yahoo.com>
To: jay alvarez <ldapb0y@yahoo.com>
Message-id: <44274325.4020900@sun.com>
Organization: Sun Microsystems Inc.
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7BIT
User-Agent: Thunderbird 1.5 (Windows/20051201)
References: <20060327012317.28213.qmail@web38904.mail.mud.yahoo.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2
Cc: ldapext@ietf.org
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org



jay alvarez wrote:
> Good day,
>
> I have some questions regarding draft-behera-ldap-password-policy-08.txt.
>
> 1. Do you know if it has been standardized or updated yet?
Not yet. We've been discussing about the password policy at last IETF 
and we need to collect information about the various implementations, 
see if we can reach consensus on common set of features.
> 2.In pwdCheckQuality, it says  it is still in TODO list..
Right now, pwdCheckQuality is an integer that tells whether quality of 
the password must be checked or not. What quality means and how it's 
configured is left to implementation.
Several persons have expressed the desire to have common definition for 
password quality. We have not reached consensus on this subject.

> Do you know how to enforce the minimum included characters like it 
> must have Upper, lower, number, special characters without 
> administrator intervention? Sure, I can use some random password 
> generation tools to enforce these requirements but I'm thinking a lot 
> of negative implications..
>
> 3. how does expiration warning shown to the user?? Let's say, I would 
> do an ldapsearch in the commandline and do a simple bind... it didn't 
> tell me if my password is about to expire even if I run it in verbose 
> mode..
ldapsearch would have to have support for the password policy controls. 
Which ldapsearch tool did you use ?
>
> 4. What if in pwdMustChange, the user did not change his password 
> after initial bind or reset by administrator?? What will happen?? The 
> attribute explanation doesn't say anything about this....

Our implementation will reject any other operations on that connection.
>
> 5. How to send old pa! ssword when changing to a new 
> password(pwdSafeModify)??
> I've looked into ldapmodify and found nothing about this.
> My file looks like this:
>
> dn: uid=jayson,ou=people,o=example,dc=com
> changetype: modify
> replace: userPassword
> userPassword: {SSHA}g/pfweYQQRtYFxVGwhn8xnCCEcY0rDTDQ
>
dn: uid=jayson,ou=people,o=example,dc=com
changetype: modify
delete: userPassword
userPassword: OldPassword
add: userPassword
userPassword: NewPassword

Or you could use the Password Modify Extended operation.

Regards,

Ludovic.


> On ldapmodify operation, I got this error:
> ldap_modify: Insufficient access (50)
>         additional info: Must supply old password to be changed as 
> well as new one
>
>
>
> That's all for now, thanks!
> -jay
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Ldapext mailing list
> Ldapext@ietf.org
> https://www1.ietf.org/mailman/listinfo/ldapext
>   

-- 
Ludovic Poitou                                    Sun Microsystems Inc.
Software Architect                               Directory Server Group
http://blogs.sun.com/Ludo/                             Grenoble, France

Sun Microsystems requires the following notice:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
NOTICE:  This email message is for the sole use of the intended
recipient(s) and may contain confidential and privileged information.
Any unauthorized review, use, disclosure or distribution is prohibited.
If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Mon Mar 27 23:18:50 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FO5fK-0003Dy-Ke; Mon, 27 Mar 2006 23:18:46 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FO5fJ-0003Do-GQ
	for Ldapext@ietf.org; Mon, 27 Mar 2006 23:18:45 -0500
Received: from web38913.mail.mud.yahoo.com ([209.191.125.119])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1FO5fH-0005gH-Tt
	for Ldapext@ietf.org; Mon, 27 Mar 2006 23:18:45 -0500
Received: (qmail 60907 invoked by uid 60001); 28 Mar 2006 04:18:43 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding;
	b=lQ/8Z3QzpD+qg54ptMOSI4GRAj8cbI7NEozhoVPEGL1D+TNf1PFHiXfd9D6JFMR6mNtbeIfn1v2dvf/w9PBuLTU0o4W+YmrJI47hPLQln7urlOJDLMKVdMya1PBCvdCllV01Dcjy0hXIR9ZNDkYkCcZhhCmyxKpP+FbrA74lTis=
	; 
Message-ID: <20060328041843.60905.qmail@web38913.mail.mud.yahoo.com>
Received: from [202.90.128.28] by web38913.mail.mud.yahoo.com via HTTP;
	Mon, 27 Mar 2006 20:18:43 PST
Date: Mon, 27 Mar 2006 20:18:43 -0800 (PST)
From: jay alvarez <ldapb0y@yahoo.com>
To: Ldapext@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Cc: 
Subject: [ldapext] possible denial of other users account (when
	pwdLockout=True)
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

Hi,

when pwdLockout is set to True in ppolicy, then users
my use other users "username" and provide an invalid
password, login a couple of times until the account of
that poor user is locked.. Any suggestion about this?

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



From ldapext-bounces@ietf.org Tue Mar 28 02:25:13 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FO8ZX-0007rR-3K; Tue, 28 Mar 2006 02:24:59 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FO8ZV-0007r1-0s
	for Ldapext@ietf.org; Tue, 28 Mar 2006 02:24:57 -0500
Received: from 197-0-124-83.dsl.3u.net ([83.124.0.197]
	helo=srv1.int.stroeder.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FO8ZT-0003ma-I9
	for Ldapext@ietf.org; Tue, 28 Mar 2006 02:24:56 -0500
Received: from localhost (localhost [127.0.0.1])
	by srv1.int.stroeder.com (Postfix) with ESMTP id 750942378;
	Tue, 28 Mar 2006 09:24:53 +0200 (CEST)
Received: from srv1.int.stroeder.com ([127.0.0.1])
	by localhost (srv1 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
	id 21467-07; Tue, 28 Mar 2006 09:24:46 +0200 (CEST)
Received: from [10.1.1.5] (unknown [10.1.1.5])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client CN "Michael Stroeder",
	Issuer "Thawte Personal Freemail Issuing CA" (not verified))
	by srv1.int.stroeder.com (Postfix) with ESMTP id 967462214;
	Tue, 28 Mar 2006 09:24:45 +0200 (CEST)
Message-ID: <4428E4C0.3030706@stroeder.com>
Date: Tue, 28 Mar 2006 09:24:48 +0200
From: =?ISO-8859-1?Q?Michael_Str=F6der?= <michael@stroeder.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050920
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: jay alvarez <ldapb0y@yahoo.com>
Subject: Re: [ldapext] possible denial of other users account (when
	pwdLockout=True)
References: <20060328041843.60905.qmail@web38913.mail.mud.yahoo.com>
In-Reply-To: <20060328041843.60905.qmail@web38913.mail.mud.yahoo.com>
X-Enigmail-Version: 0.93.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: amavisd-new at int.stroeder.com
X-Spam-Score: 0.1 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: Ldapext@ietf.org
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ldapext>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ldapext>,
	<mailto:ldapext-request@ietf.org?subject=subscribe>
Errors-To: ldapext-bounces@ietf.org

jay alvarez wrote:
> 
> when pwdLockout is set to True in ppolicy, then users
> my use other users "username" and provide an invalid
> password, login a couple of times until the account of
> that poor user is locked.. Any suggestion about this?

Many security people are not aware of this problem. In real life you
could lock down big companies with a small script if you know the user
IDs and such a "strict" password policy with infinite failure lock is in
effect.

I've argued so many times to let the server unlock the account
automatically after a short time (see pwdLockoutDuration). But people
does not seem to take this problem seriously enough.

Ciao, Michael.

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext



