setting up webdav server mac os x server

Setting up webdav server mac os x server software#
Setting up webdav server mac os x server download#
Setting up webdav server mac os x server windows#

All WebDAV functions are encoded in XML, and mod_dav will attempt to parse the requests in RAM ”again leading to a resource usage problem and potential DoS condition. Sets a limit on the size of the XML request that the client can send. Can be used either globally or in an Apache container. This will prevent remote machines from collecting (recursively) information about every resource under the WebDAV share, potentially using a great deal of server resources and possibly creating a denial of service condition. If off (the default), mod_dav will not allow infinite depth commands to be processed. The standard Apache access directives are still needed to control security for the resource. Used in an Apache container, this directive enables WebDAV support within that container. May be used within an Apache container or globally in nf. The minimum lifetime of a file lock in seconds. This is a global directive that should be used once in the /etc/httpd/nf file. The path and base file name (such as /var/tmp/moddavlock ) that will be used for mod_dav lock files. The mod_dav module adds several special directives to the Apache configuration that you'll need to use to set up your WebDAV shares.

Setting up webdav server mac os x server download#

If you would like to download and compile mod_dav by hand, it is available from. Apache 2.0 incorporates mod_dav in the base distribution, so this won't even be a consideration when Apple makes the migration to the new server in the future.

Setting up webdav server mac os x server software#

Normally we would recommend that software be installed from scratch, but because the mod_dav code has remained largely static for the past two years this seems unnecessary. Remove the comments from both lines, so that they read LoadModule dav_module libexec/httpd/libdav.so AddModule mod_dav.c NOTE Look for the (noncontiguous) lines #LoadModule dav_module libexec/httpd/libdav.so #AddModule mod_dav.c

You need to do this as root to make changes. To enable WebDAV, edit the file /etc/httpd/nf. Large recursive requests can be sent to the server, using up resources and potentially resulting in a DoS attack.Īlthough you can deal with the first two issues with basic system administration skills, the third may require fine-tuning the mod_dav DAVDepthInfinity and LimitXMLRequestBody directives, discussed shortly. Users can store arbitrarily large files on the server, eating up disk space. mod_dav runs with the Apache server permissions, meaning files/directories that can be written to by the www user or group can be modified through WebDAV. Improper file permissions can lead to files being modified that shouldn't be. But given that you take the precautions listed in the installation document, Apache and mod_dav are quite secure.Īlthough there are no known exploits of mod_dav, there are several potential problems: You can misconfigure your Apache/ mod_dav system (in fact, SuSE Linux released an RPM like this and had to issue a security advisory and upgrade). There has not been a single reported exploit of the code in the past three years (when it was first released). WebDAV Security HistoryĪs far as security goes, consider this statement, taken from the mod_dav FAQ:Īpache and mod_dav are quite secure. Instead, it piggybacks on HTTP, using the Apache server process and all its access controls to manage who can access what. WebDAV is unique in that it doesn't introduce another protocol or server process to your machine. Mac service provides iDisk access via WebDAV, and the Mac OS X Apache distribution includes mod_dav, enabling your machine to serve other Linux, Windows, and Mac clients. It as well as everyone at the office is on a Private IP range behind a firewall.WebDAV (Web Distributed Authoring and Versioning) is another popular form of file sharing built into Mac OS X.

Setting up webdav server mac os x server windows#

the server's name to itself is 'localhost' (while it actually has a name to the Windows boxes for Windows File sharing). DNS is not active (or if it is, it's not configured), If I type in an address, the dialog box goes away (without any confirmation) but does not publish either.Ī few things to note, that I have not done as of yet because we don't need to use internally are: I've tried it for the root web host, and for a user's (/~user) website - no luck! So I type in the URL enter a username and password. ICal can NOT publish to the server (and simply says 'Connot publish'). So iCal says it works with 'any WebDAV server', I go to the server and enable Web Hosting, I go further in and enable WebDAV hosting. Since we have a OSX 10.2 Server in the office, I decided to play with iCal and see about setting up internal calendars among other things I've been wanting to create for internal use only. For the life of me I can't figure this one out.