From dev-return-38249-apmail-directory-dev-archive=directory.apache.org@directory.apache.org Tue Jun 7 06:10:40 2011 Return-Path: X-Original-To: apmail-directory-dev-archive@www.apache.org Delivered-To: apmail-directory-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0754C6970 for ; Tue, 7 Jun 2011 06:10:40 +0000 (UTC) Received: (qmail 59821 invoked by uid 500); 7 Jun 2011 06:10:38 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 59648 invoked by uid 500); 7 Jun 2011 06:10:27 -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 59622 invoked by uid 99); 7 Jun 2011 06:10:22 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Jun 2011 06:10:22 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of elecharny@gmail.com designates 74.125.82.178 as permitted sender) Received: from [74.125.82.178] (HELO mail-wy0-f178.google.com) (74.125.82.178) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Jun 2011 06:10:14 +0000 Received: by wyb33 with SMTP id 33so4142554wyb.37 for ; Mon, 06 Jun 2011 23:09:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:reply-to:user-agent :mime-version:to:subject:content-type:content-transfer-encoding; bh=/9Z6cbbTZgCr3+xG7tdoPFg0wxXHIoP6Rof+cGnWIK0=; b=KS1C4O+nbqr8vbJ+VYSsCoGlK+TBjXY3QLka6/Mhu5SvcgihUmlCnxKWI3GenMxKre ZxZ/y/afPMn/v6XXK1Sw3nxZleznTtTgetaXxYLDu3ip5gzrDQy/XTe+y68SdBs/mJCe DuvJC3JGwJUjHiYBBWPjiNoS8fCrX2qqRe238= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; b=c8UaB3qZcnm2bOFqbrZ369G5v1CFBGBecXugH5PT1EbPANz8777Iy568oq8lvu0Kdn +QaNxESU1DuhTlJ4uXSTWf/Y+7BZAePMTZISg4wJ/8nbzFJwAw7kjaz+KEcs+f966nrs 0eaSF6I+iqaRye3ZsD1Hjmxi/FjwbvXPwumIo= Received: by 10.217.1.5 with SMTP id m5mr5776936wes.19.1307426993890; Mon, 06 Jun 2011 23:09:53 -0700 (PDT) Received: from emmanuel-lecharnys-MacBook-Pro.local (lon92-10-78-226-4-211.fbx.proxad.net [78.226.4.211]) by mx.google.com with ESMTPS id f73sm2660568wef.43.2011.06.06.23.09.52 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 06 Jun 2011 23:09:52 -0700 (PDT) Message-ID: <4DEDC0AF.4080503@gmail.com> Date: Tue, 07 Jun 2011 08:09:51 +0200 From: Emmanuel Lecharny Reply-To: elecharny@apache.org User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 MIME-Version: 1.0 To: Apache Directory Developers List Subject: Values normalization and special characters Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org Hi guys, I'm a bit deeper into the DN/RDN problem. Now, the issue I have is that I don't know how we should handle shuch case : - an AT like "cn: \ user" having an escaped space at the beginning. - an entry which DN is "cn=\ user,ou=system" The check is done internally comparing the RDN ("cn=\ user") and the Attribute value. Sadly, when we parse the DN, we remove the '\' (as it's not significant), keeping the leading space. But then, we normalize the RDN applying the CN normalizer to it, which removes the leading space. At this point, we are in a dead end... Either we keep the '\' in the RDN, but that would make the comparison complex, or we consider that escaped spaces are just insignificant, but we breach the RFC. However, leading spaces and trailing spaces are most certainly not useful, so breaking the RFC would be acceptable, IMO. Do you have any better idea ? Note : there is no place in the RFC where we are told how to manage attribute values with escaped chars... (still have to check though...) -- Regards, Cordialement, Emmanuel Lécharny www.iktek.com