[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
LDIF and structural objectclasses
- To: openldap-software@OpenLDAP.org
- Subject: LDIF and structural objectclasses
- From: Daniel Tiefnig <dantie@gmx.at>
- Date: Wed, 23 Apr 2003 23:42:38 +0200
- User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030312
Hi there,
if been reading RFC2849 for some time now, and I'm wondering about some
things.
1) Why are userpassword attributes always encoded in base64 in
OpenLDAP2.x.x? e.g. "{crypt}c4jHzc08CN.ug" is a valid SAFE-STRING, but
is encoded anyways.
2) I'm not sure that I'm understanding that '*', '1*' and '0*1' thingy
correctly. AFAICT '*' means as many as wanted and '1*' means as many as
wanted but at least one. But WTF is '0*1'?
3) FAQ-O-Matic says "Object class violation (65)" with "additional info:
invalid structural object class chain (qmailuser/person)" means "Two or
more structural objectClass values listed are not related."
Why's that an error actually? (And since when, have never seen this so far.)
TIA,
daniel