Ok, it took a certain amount of fiddling on my part because I was trying to get it to authenticate with PAM and had also broken my virtual host config at the same time but basically here's what I did:
I'll assume that you're able to connect to the bubba via ssh and are happy editing text files and navigating your way around a linux system and that you've enabled the main debian package repositories. If you are not then you might want to rethink your plan...
1) The apache webdav module is already installed as part of apache2, so just need to enable the relevant modules - as root do:
2) Install the apache2 PAM module:
Code: Select all
apt-get update && apt-get install libapache2-mod-auth-pam
Edit: I forgot (see next post) to enable the AuthPAM module:
Add the www-data user to the shadow group so that the apache server can read the shadow file to authenticate users (NB this does have a security implication in that if you misconfigure your apache2 it might be possible for remote users to download your shadow passwords file).
You want to edit /etc/group/ so that the lentry for the shadow group reads:
3) I decided to enable webdav on the default https web-server as I don't use the bubba for its PIM functionality outside of my local network so can live withut needing the SSL web server for anything else. It's probably a good idea to use an SSL enabled server for WebDAV if you are connecting to it remotely as otherwise you'll be sending user credentials unencrypted over an untrusted network.
I edited /etc/apache2/sites-enabled/bubba to change the https virtual host:
Change the document root to be /home to enable access to all home directories
Edit the root directory config section:
Code: Select all
<Directory />
DAV on
AuthPAM_Enabled on
AuthType Basic
AuthBasicAuthoritative Off
AuthName "PAM"
require valid-user
AuthUserFile /dev/null
4) With any luck, if I've not missed some important step out (!), then when you restart the web-server:
You should have a webdav server running on port 443 that you can use to access the home and storage directory using your normal login and password. Probably a sensible thing to do would be to restrict the user accounts a bit more in the apache confoiguration to stop a root login via webdave.[/code][/b]