OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
Re: WebDAV locking trouble (yes, DavLockDB is chroot relative)

From: Nick Forrette (foreheadgmail.com)
Date: Wed Mar 01 2006 - 10:43:16 CST


On 2/28/06, Nick Forrette <foreheadgmail.com> wrote:
>
> From: foreheadgmail.com
> Subject: httpd / mod_dav locking troubles (DavLockDB is
> chrooted
> relative)
> Date: February 28, 2006 7:21:59 AM PST
> To: foreheadgmail.com
>
>
> I'm running OpenBSD 3.8 stable with mod_dav 1.0.3p0 installed from
> ports (sparc64 architecture).
>
> My goal is to get mod_dav working over https. While https is working
> ok, and my DAV client (Mac OS X 10.4.5) can connect and authenticate,
> any time the client attempts to create a file it will hang. Examining
> the error_log shows the following message repeated many thousands of
> time (before I killed httpd and waited for the Mac to timeout):

Last night I recompiled httpd and mod_dav with debugging enabled, and ran
httpd in gdb with arguments "-X -DSSL -f /var/www/conf/httpd.conf". I set a
breakpoint in sdbm_store, which was the routing that was failing with errno
= EINVAL. After a little digging, I found the following:

mod_dav constructs a dbm key based (at least in part) on the file name being
locked. However, the file name used to construct the key was always the
empty string. Looks a lot like there is a bug in mod_dav.

I'm relatively new to the DAV and OpenBSD communities, and am wondering if
it makes more sense if I take this up on either the port-bugs or the dav-dev
list.

Thx,
Nick