Closed Bug 282608 Opened 20 years ago Closed 20 years ago

Use SVRCORE functions from either NSS or separate SVRCORE

Categories

(Directory :: LDAP C SDK, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: richm, Assigned: mcs)

Details

Attachments

(1 file, 1 obsolete file)

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040805 Netscape/7.2
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040805 Netscape/7.2

The internal ldap c sdk builds we do for Red Hat (and prior to that Netscape,
and probably still at Sun) use a library called SVRCORE.  It provides two
services, only one of which is used in the ldap sdk - the pin management
services.  These are defined in a header file called svrcore.h.  The other
service is server side SSL set up, in servssl.h, which is old, crufty, and
apparently hasn't been used in a long time.

I'm working on moving SVRCORE into NSS.  We need to be able to build the LDAP C
SDK with SVRCORE pin management, either by using the old SVRCORE or the new NSS
library.

Reproducible: Always

Steps to Reproduce:
Attached file Diffs to use NSS SVRCORE (obsolete) —
Not much here - it mostly just works as is.
I moved HAVE_SVRCORE into the "external" world since it is now an external
component.
I removed some old forte6 /s/b/c cruft from a Makefile.
I used DEFS+= instead of CFLAGS+= because CFLAGS was not working for me for
some reason and DEFS makes more sense.
Comment on attachment 176213 [details]
Diffs to use NSS SVRCORE

Looks OK to me.  I am surprised there is a problem with CFLAGS though.
Attachment #176213 - Flags: review+
I am surprised too.  But this happened to me more than once (on Red Hat EL 3).
After this checkin, I'll do a quick review of bugs to see if there are any which
we should get in for DS 7.1.  Then I'll need to tag the tree.
Attached file Newer diffs
Here is a better diff.	It also updates the components - NSS 3.9.3, NSPR 4.4.1,
DBM 1.61.
Attachment #176213 - Attachment is obsolete: true
If these diffs are ok, I'd like to tag the tree.  I think the next release
number would be 5.15?  Is there anything I need to change in the ldapcsdk tree
to bump the version number?  The 5.15 release would contain: fix for getpassword
on HP-UX; allow use of open source SVRCORE; update component versions.
Comment on attachment 176974 [details]
Newer diffs

The patch looks good.  Please commit.  The version can be set at build time,
which is what we have typically done in the past.  It would be nice to update
it in the source code too; just change the VENDOR_VERSION variable in
mozilla/directory/c-sdk/build.mk
Attachment #176974 - Flags: review+
Make that DEFAULT_VENDOR_VERSION.
Done.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: