Comments on: Automatically Mounting WebDAV in Ubuntu with a FuseDAV Init Script

By: Jamie Talbot

Jamie Talbot — Thu, 28 Jul 2011 13:45:00 +0000

Hi,

Yeah, it’s not perfect. As I note above, because you type the password on the command line it is plainly visible in many ways – even htop will reveal it. I’m not aware at the moment of anyway of calling fusedav without specifying a password. Would be happy to hear otherwise.

As for permissions, off the top of my head, you could create a low privilege account and give it ownership of the mount. Then, instead of using sudo the command in the init script, use su newaccountname -c ‘fusedav …’

I haven’t tried this however.

Hope this helps somewhat.

Cheers,

Jamie.

By: Curious

Curious — Thu, 28 Jul 2011 12:05:00 +0000

Interesting article. Thanks for the pointers. Seems to work ok. A couple of issues:

ps -ef | grep fuse

reveals the username and password of the dav share to all users. Not so secure.

Also, I’d be interested to know if you have ideas for managing permissions on the local mount so that an ordinary user might be allowed access?

Thanks again.

By: Automatically Mounting WebDAV in Ubuntu with a FuseDAV Init Script | TurboLinux Blog

Tue, 21 Jun 2011 11:59:17 +0000

[...] Here is a good tutorial show you how to Automatically Mounting WebDAV in Ubuntu with a FuseDAV Init Script: the face of it, davfs2 is more convenient, as it allows you to automount quite easily using fstab. However, despite a number of attempts, I couldn’t convince it to allow me to write files remotely, only folders. It seems a number of people have had the same issue. [...]

By: Prosper

Prosper — Sun, 20 Feb 2011 19:29:00 +0000

Thanks a lot. This really saved my day.I had but one inconvenience and that is that the share was only readable by root. Since I do not like running Nautilus as root, I removed the script from startup and start it manually as a normal user. Of course, I had to change permissions on the file with the URL and password information, but it is reasonably well hidden. In order to create the .pid file I also had to make /var/run writable.

By: Jamie Talbot

Jamie Talbot — Thu, 10 Feb 2011 23:26:00 +0000

Hi Andras,

Couple of things to try. Firstly, try the script exactly as is (i.e., without renaming bingo) and see if that works. If that works then you can move onto renaming. Have you granted +x permissions on /etc/init.d/your-name ? Have you changed $NAME in /etc/init.d/your-name to ‘your-name’?

The final code block in the post shows an example of how to take a working mount definition ‘bingo’ and copy it to create another one. Did that work? If you don’t want the bingo script lying around, you can use ‘mv’ instead of ‘cp’ on the first line.

Hope that helps a bit…

By: Andras

Andras — Tue, 08 Feb 2011 15:40:00 +0000

Great post.
I tried mount.cifs, davfs2, all of them gave me heart ache. Followed you post, was easy and looks like it works. I have run into one problem and not sure if I can ignore it:
after executing the : su /etc/init.d/bingo start #(I changed the name from bingo…)
got the following error msg: Unkown id: /etc/init.d/bingo

checked the var/run directory > there is no bingo.pid file
checked the script and it says in the start section: and it the PID file does not exist it should create it. Do you have any idea what is wrong?

thanks
Andras

do_start()
{
# Return
start-stop-daemon –start –quiet –pidfile $PIDFILE –exec $DAEMON –test > /dev/null
|| return 1

set — $(cat ${MOUNT_FILE})
URI=$1
USERNAME=$2
PASSWORD=$3

DAEMON_ARGS=”-u $USERNAME -p $PASSWORD $URI $MOUNT_POINT”

start-stop-daemon –start –quiet –pidfile $PIDFILE –background –make-pidfile –exec $DAEMON —
$DAEMON_ARGS
|| return 2
}

By: Jamie Talbot

Jamie Talbot — Sat, 29 May 2010 04:38:13 +0000

Hi Jerome,

Don't know the answer to this I'm afraid – I noticed the same thing, but as I was the only user of the box it wasn't too much of an issue for me. If you find out though, please let me know!

By: Jerome

Jerome — Thu, 27 May 2010 19:54:23 +0000

Thank you for this post! This is exactly what I wanted. My only issue is that the FuseDAV drive is mounted with root:root as the owner and group and when I attempt to “chown it” I get an error. Is there a way for this to be mounted with root:users as the owner and group?