[DA][Fwd] LDAPS support (and some more stuff)

Hello
Either I'm a stupid or something isn't right with diradmin-dev... I'm
forwarding(/resending) my own mail to this list instead (even though I
think this is really a -dev mail).
Cheers
Fredrik (aka scientica)

---------- Forwarded message ----------
From: scientica (GMail) <[email protected]>
Date: Jul 17, 2005 9:56 PM
Subject: LDAPS support (and some more stuff)
To: [email protected]
Cc: Mike Jackson <[email protected]>


Hi (whoever read this)

First of all, a "sanity check" *read all of this e-mail before doing
anything said bellow* (yes I will test if you've done so bellow)

I've been hacking the sources a while now and managed to implement LDAPS
support (LDAPS = Secure LDAP), I've also added some extra stuff (like
debug macros, 2 switches to ./configure, namely --disable-ldaps
(disables the newly implemented LDAPS support) and --enable-debug
(enables debugging messages).
I've attached 2 files:
1.6.0-scientica_ldaps_patch_1.tbz2 - the whole branch (399KB)
1.6.0__to__1.6.0-scientica_ldaps_patch_1.diff.bz2  - the diff between
the "vanilla" 1.6.0 sources and my branch* (142KB)

*apply this way: extract the vanilla sources to a dir, cd to that dir,
then run "bzcat
/path/to/1.6.0__to__1.6.0-scientica_ldaps_patch_1.diff.bz2 | patch -p0
&& find -type d -name CVS -exec rm -fr {} \;" (ignore 'errors' like
"find: ./macros/CVS: Filen eller dir doesn't exist")

to compile the debug-ready version first edit the file named
"config_debug", change the "k8" to what ever applies to your CPU (use
i386 if you don't know, or keep k8 if you're using an AMD64), then run
this line in the extracted directory:
# . ./create_automake_havock.sh && . config_debug && make -j3
**************************************************************************************
* WARNING RUNNING THIS VERSION IS INCOMPATIBLE WITH THE CURRENT
CONFIGURATION FORMAT *
**************************************************************************************
so, in short, backup your ~/.directory_administrator/profiles *before*
running it!
Then run ./src/directory_administrator (at your own risk)

I've (tried) to make a short README.BRANCH and a TODO.BRANCH, the readme
file tries to explain what I've done. The TODO mentions a
"happens-at-random" bug, I think I have fixed it by adding a "sleep(1);"
before a "fclose(fd);" - though, I just suspect that somehow fixed it
(haven't had any freezes since I added that line).
I would like to force everyone that even thinks about compiling this
version to read the README.BRANCH, especially the "Misc" section, where
it mentions something about the config file format-backwards
compabillity beeing breaked with this branch.

Any comments or questions are welcome. I belive that this branch is not
yet "production stable/ready", since it's not been fully tested and
since it breaks backwards compabillity with the configuration file
"~/.directory_administrator/profile".
Also, I'd really like to hear your comments on the debug macros (and the
add of --enable-debug which defines DEBUG so we can do things like
"#ifdef DEBUG", the DBG_PRINT and DBG_PRINT_DM are only printing debug
data when DEBUG is defined, thus when configure was run with
--enable-debug). And I've not done any specific tests with --disable-ldaps.

oh, I just remembered, I've not added my self to the CREDITS file...

Now, you can try to compile it if you trust me. (this is the "test"
mentioned in the second sentace - haven't we all done the test where the
first line reads "care fully read all instructions before starting the
test", and after 5 mintues people start erasing their answers as the
final line reads "only fill in question number 1 before handing the test
in" :)
btw, did I mention that this branch breaks the
~/.directory_administrator/profile with a changed format for this file?

Best Regards
Fredrik (aka scientica)

p.s. Mike Jackson, I'm sorry to bother/cc you, I just wonder if this
e-mail really end up in the diradmin-dev list (could you please e-mail
me either way and tell me?). TIA

--
After all, if you are in school to study computer science, then a
professor saying:
 "use this proprietary software to learn computer science" is the
same as English professor handing you a copy of Shakespeare
and saying:
 "use this book to learn Shakespeare without opening the book itself."
  -- Bradley Kuhn





-- 
... a professor saying: "use this proprietary software to learn
computer science" is the same as English professor handing you a copy
of Shakespeare and saying: "use this book to learn Shakespeare without
opening the book itself.
- Bradley Kuhn