From dev-return-25035-apmail-directory-dev-archive=directory.apache.org@directory.apache.org Mon Apr 21 23:23:03 2008 Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 15150 invoked from network); 21 Apr 2008 23:23:02 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 21 Apr 2008 23:23:02 -0000 Received: (qmail 6241 invoked by uid 500); 21 Apr 2008 23:23:03 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 6205 invoked by uid 500); 21 Apr 2008 23:23:03 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 6194 invoked by uid 99); 21 Apr 2008 23:23:03 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 Apr 2008 16:23:03 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of akarasulu@gmail.com designates 209.85.198.226 as permitted sender) Received: from [209.85.198.226] (HELO rv-out-0506.google.com) (209.85.198.226) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 Apr 2008 23:22:20 +0000 Received: by rv-out-0506.google.com with SMTP id g37so1096179rvb.25 for ; Mon, 21 Apr 2008 16:22:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth; bh=PnZN2YodOd+VgG+wDDwUCPbOXXccOn5dZM97g3kARow=; b=Ize15N8SnMdFRPHQQoWSEqO3gTHg87DwJDCCPlesVeiMpmm0dL0T7ySM+KLJOObDCp/a3FmUU9izOdxFtyQ6A+mDtkBDEMgAOy76T1tBZd1WeSfYgfXngWqUcCIeLCn0nkUV5Vd5nu6m7sNyyz4DKVXxxyVGuIDD4LVaZSBR2ps= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=o8nxIMQ5tyHvtF1fDPjA3hyDo6nqx0/zSmR7MayRTgz8lN3mWzPOfEqOnMmGtIB+WXrjMg26UtwGc9Z9pMKZkJi7toXz4LMJ8zkuWgxKnKO+xGGoAVUTGuXB3OkI+1WfiOP/t+jOC1KqhCiWCgNsHB5LHqkFG/kX5nkypY5r1/k= Received: by 10.140.191.14 with SMTP id o14mr3648290rvf.247.1208820154047; Mon, 21 Apr 2008 16:22:34 -0700 (PDT) Received: by 10.141.113.13 with HTTP; Mon, 21 Apr 2008 16:22:34 -0700 (PDT) Message-ID: Date: Mon, 21 Apr 2008 19:22:34 -0400 From: "Alex Karasulu" Sender: akarasulu@gmail.com To: "Apache Directory Developers List" Subject: Re: Injection of invalid ObjectClasses... In-Reply-To: <480D16F1.8000202@gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_9848_10281166.1208820154043" References: <480D16F1.8000202@gmail.com> X-Google-Sender-Auth: a1713abe7d688e3f X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_9848_10281166.1208820154043 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi E, On Mon, Apr 21, 2008 at 6:36 PM, Emmanuel Lecharny wrote: > Hi, > > just wanted to have a second thought. Here is what bugs me : > > - we have a valid entry > - we modify it with a new ObjectClass, which is not valid ( "test", for > instance) > You mean to say: (1) the objectClass does not exists? (2) objectClass exists but the modification does not include the required MUST attributes associated with the new objectClass? > > Q1 : should the server accept this? > In either of the cases #1 & #2 above I think the modification should be rejected with an error. > > My personnal guess would be : no, but the DIRSEVER-791 test accept it. So > Q2: Should we modify the test accordingly to my guess ? > Yeah it will need to change then I agree. Stefan Z. you have any thought on this? Alex ------=_Part_9848_10281166.1208820154043 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi E,

On Mon, Apr 21, 2008 at 6:36 PM, Emmanuel Lecharny <elecharny@gmail.com> wrote:
Hi,

just wanted to have a second thought. Here is what bugs me :

- we have a valid entry
- we modify it with a new ObjectClass, which is not valid ( "test", for instance)

You mean to say:

(1) the objectClass does not exists?
(2) objectClass exists but the modification does not include the required MUST attributes associated with the new objectClass?
 

Q1 : should the server accept this?

In either of the cases #1 & #2 above I think the modification should be rejected with an error.
 

My personnal guess would be : no, but the DIRSEVER-791 test accept it. So
Q2: Should we modify the test accordingly to my guess ?

Yeah it will need to change then I agree.  Stefan Z. you have any thought on this?

Alex

------=_Part_9848_10281166.1208820154043--