[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ldap
Subject:    [ldap] Re: Equality and Syntax questions
From:       "T I" <openbsd_inquiry () yahoo ! com>
Date:       2005-10-23 8:57:00
Message-ID: 200510230858.j9N8w3nX022323 () mailer ! progressive-comp ! com
[Download RAW message or body]


Sorry if I'm coming across totally new(bie) I am.  OpenLDAP rocks and my
project(also open source) rocks!  I have just come across the the recent
post of Sanjay Sutar with response provided by Hallvard B Furuseth
regarding "attribute in encrypted format."

Date: Fri, 14 Oct 2005 10:44:24 +0200
Subject: Re: attribute in encrypted format
http://listserver.itd.umich.edu/cgi-bin/lyris.pl?sub=3144733&id=288539181

So while there is "no standard syntax for encrypted values" LHEX and
HEX(digest message hashes, signatures and keys created through the use of
md5, sha1 and ssh-keygen in OpenBSD) are different animals syntactically
and there is no way to enforce a particular data definition on that being
stored.  I am assuming that these values are all the same.

To roughly quote Hallvard B Furuseth, "OCTET STRING or IA5 syntax may be
used" and I add that those definitions will not constrain the data to LHEX
or HEX and in fact the data may include other possible values.  If so,
that's cool.  It is the answer that I am looking for and I have a place to
begin.

My bad if I have driven everyone to the brink of madness.  Were, like,
er., neighbors now!  ;-)


Thanks!

P.S. Did all of the LDAP list managers take the weekend off to go to the
World Series?  If so...Go WhiteSox!

---
You are currently subscribed to ldap@umich.edu as: [ldap@progressive-comp.com]
To unsubscribe send email to ldap-request@umich.edu with the word UNSUBSCRIBE as the \
SUBJECT of the message.


[prev in list] [next in list] [prev in thread] [next in thread]