I am agreeing that you can think the problem is OpenSSL issue also. But I
just thought someone from Netscape might have the solutions for this. I
believe someone ran into this problem before, as Netscape LDAP SDK and
OpenSSL is very popular.
One of the name conflict is MD5_Update(...).
Do you know someone working on this issue? any one..
The link you point to doesn't have the SSL part, right?
Thanks
Elwin
-----Original Message-----
From: Michael Hein [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 02, 2001 12:31 PM
To: [EMAIL PROTECTED]
Subject: Re: LDAP SDK name conflict with Openssl
"HO,ELWIN , HP-Cupertino,ex1" wrote:
> Hi,
>
> I have a project about authenticate user to access web resource by using
> Apache web server and aut_ldap.
>
> I build the LDAP Apache module(auth_ldap) with Netscape LDAP SDK 4.1. (Our
> Apache built with OpenSSL 0.96a) There aren't problems to build the
module,
> but the web server cannot start after I add the module to the web server.
> The answer I got from the module author is that Openssl have name conflict
> with Netscape LDAP SDK.
>
Can you please provide the details as to what conflict you have and your
assessment as to why it is a LDAP SDK issue and not an Openssl issue. The
latest source code for the C SDK can be found at
http://www.mozilla.org/directory/csdk.html
Michael
>
> My questions are
> 1. Are there any fixed for this?
> 2. Where I can get the entire Netscape LDAP SDK source code (Include
> security part)?
> 3. Does Netscape LDAP SDK use PKCS #12 for encryption?
> 4. Can I change pkcs to Bsafe?
>
> Thanks
> Elwin Ho
