RE: Liberal parsing of schema elements (ITS#1996)

[hyc@symas.com]

I believe the older code allowed these definitions, but with rev 1.42
of schemaparse.c this behavior was removed, so valid OIDs are always
required.

  -- Howard Chu
  Chief Architect, Symas Corp.       Director, Highland Sun
  http://www.symas.com               http://highlandsun.com/hyc
  Symas: Premier OpenSource Development and Support 

> -----Original Message-----
> From: owner-openldap-bugs@OpenLDAP.org
> [mailto:owner-openldap-bugs@OpenLDAP.org]On Behalf Of
> michael@stroeder.com
> Sent: Tuesday, July 30, 2002 5:11 AM
> To: openldap-its@OpenLDAP.org
> Subject: Liberal parsing of schema elements (ITS#1996)
> 
> 
> Full_Name: 
> Version: REL_ENG_2_1
> OS: Linux
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (62.224.170.55)
> 
> 
> OpenLDAP usually is very strict regarding schema parsing but 
> provides some flags
> to be more liberal (constants LDAP_SCHEMA_ALLOW_* in ldap_schema.h).
> 
> But even if LDAP_SCHEMA_ALLOW_ALL is used e.g. the following object class
> definition is not accepted:
> 
> objectClasses: ( inetsubscriber-oid NAME 'inetSubscriber' SUP top 
> AUXILIARY MAY ( inetSubscriberAccountId $ inetSubscriberChallenge $ 
> inetSubscriberResponse ) X-ORIGIN 'Nortel subscriber interoperability')
> 
> Yes, this definition does not provide a proper OID which violates LDAPv3
> standard. But unfortunately most LDAP servers contain definitions 
> like this...
>