Hello!
Last week I anounced a configuration script for easy installation of
Aolserver. Since then support for tDAV, nsldap, nsperm has been added
as well as other improvements. I am now also in touch with the Debian
package maintainer for aolserver and have included support for launching
Aolserver as a standalone daemon as is standard in this system.
While working on tDAV I found out, that I were not able to configure "/"
as a DAV-share. I even got to compare Ethereal-traces of the
Browser-Server comunications but could not succeed anyway.
At least at one place in the code I could work around a related bug:
while standard shares /dav/, for example are mangled into dav/ to create
lockfiles, the "//" share converts into "/" and the lock was created at
"/.lock".
I have modified the code, that generates the default permissions for DAV
and call a init_tDAV proc at the end of the module. This routine check
if the authentication procedure is tdav::auth::local, for the respective
server and only then initializes the nsperm - permissions.
For the lock and property directories I found a different directory
layuout which facilitates permission managment
Several features about tDAV are not clear to me yet:
- directorycmd: is a configsection param. What is it meant to do? I am
missing the directorylisting, but setting directorycmd to a respective
tcl-procedure did not yield anything.
- redirects: What are the redirects for?
- GET: is it possible to let the GET command be realized by fastpath
instead of the tDAV GET implementation?
------------
nsperm:
The init.tcl file of this module reads files from the filesystem, after
the server has start up. This, and my wish to hand over configuration
to the initial startup led me to develop an alternative approach for
permission configuration.
With my init.tcl implementation you would set up several ns_section's
for defining users, group and permissions. These are set by the initial
.tcl config file, and then read by the new nsperm - init.tcl. This
aleviates the need to manage files with credentials inside a chroot'ed
aolserver process' filesystem.
Also with nsperm I have a question:
While reading the c-code I find that the "AddUserCmd" function just
checks if the fifth argument is -allow or -deny. The rest of the
parameters are interpreted as hostnames.
However the standard init.tcl init_nsperm proc forms commandlines with
possibly several alternating -allow and -deny branches like:
ns_perm adduser usr pwd usrname -allow hosta hostb -deny hostc hostd
I hope I am just missing something here.
-----------------
Best Regards,
Jorge-Le�n
-----------
P.S.: My files are at http://www.magma.com.ni/sw/aolserver/
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]>
with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject:
field of your email blank.
