mount.davfs(8) | 1.4.6 | mount.davfs(8) |
NAME¶
mount.davfs - Mount a WebDAV resource in a directorySYNOPSIS¶
mount.davfs [-h | --help] [-V | --version]SYNOPSIS (root only)¶
mount -t davfs [-o option[,...]] webdavserver dirDESCRIPTION¶
mount.davfs allows you to mount the WebDAV resource identified by webdavserver into the local filesystem at dir. WebDAV is an extension to HTTP that allows remote, collaborative authoring of Web resources, defined in RFC 4918. mount.davfs is part of davfs2.OPTIONS¶
- -V --version
- Output version.
- -h --help
- Print a help message.
- -o
- A comma-separated list defines mount options to be used.
Available options are:
- [no]auto
- Can (not) be mounted with mount -a.
- conf=absolute path
- An alternative user configuration file. This option is
intended for cases where the default user configuration file in the users
home directory can not be used.
- [no]dev
- (Do not) interpret character or block special devices on
the file system. This option is only included for compatibility with the
mount(8) program. It will allways be set to nodev
- dir_mode=mode
- The default mode bits for directories in the mounted file
system. Value given in octal. s-bits for user and group are allways
silently ignored.
- [no]exec
- (Do not) allow execution of any binaries on the mounted
file system.
- file_mode=mode
- The default mode bits for files in the mounted file system.
Value given in octal. s-bits for user and group are allways silently
ignored.
- gid=group
- The group the mounted file system belongs to. It may be a
numeric ID or a group name. The mounting user, if not root, must be member
of this group.
- [no]_netdev
- The file system needs a (no) network connection for
operation. This information allows the operating system to handle the file
system properly at system start and when the network is shut down.
- ro
- Mount the file system read-only.
- rw
- Mount the file system read-write.
- [no]suid
- Do not allow set-user-identifier or set-group-identifier
bits to take effect. This option is only included for compatibility with
the mount program. It will allways be set to nosuid.
- [no]user
- (Do not) allow an ordinary user to mount the file system.
The name of the mounting user is written to mtab so that he can
unmount the file system again. Option user implies the options
noexec, nosuid and nodev (unless overridden by
subsequent options). This option makes only sense when set in
fstab.
- users
- Like user, but any user is allowed to unmount
the file system, not only the mounting user. This is generally not
recomended. On systems with no mtab file with the user
option unmounting by the mounting user will fail. In this case the
users may be an appropriate work around.
- uid=user
- The owner of the mounted file system. It may be a numeric
ID or a user name. Only when mounted by root, this may be different from
the mounting user.
- username=WebDAV_user
- Use this name to authenticate with the WebDAV server. This
option is intended for use with pam_mount only. When this option is set
the credentials in the secrets files will be ignored. The password will
always be read from stdin, even when option askauth is set to 0. Do
not use it in fstab. The username will be visible for everyone in
the output of ps.
SECURITY POLICY¶
mount.davfs needs root privileges for mounting. But running a daemon, that is connected to the internet, with root privileges is a security risk. So mount.davfs will change its uid and gid when entering daemon mode.
When invoked by root mount.davfs will run as user davfs2 and group
davfs2. This may be changed in /etc/davfs2/davfs2.conf.
When invoked by an ordinary user it will run with the id of this user and with
group davfs2.
Options nosuid and nodev will always be set; even root can not
change this.
For ordinary users to be able to mount, they must be member of group
davfs2 and there must be an entry in fstab.
When mounted by an ordinary user, the mount point must not lie within the home
directory of another user.
If in fstab option uid and/or gid are given, an ordinary
user can only mount, if her uid is the one given in option uid and he
belongs to the group given in option gid.
URLS AND MOUNT POINTS WITH SPACES¶
Special characters like spaces in pathnames are a mess. They are interpreted differently by different programs and protocols, and there are different rules for escaping.CACHING¶
mount.davfs tries to reduce HTTP-trafic by caching and reusing data. Information about directories and files are held in memory, while downloaded files are cached on disk.LOCKS, LOST UPDATE PROBLEM AND BACKUP FILES¶
WebDAV introduced locks and mount.davfs uses them by default. This will in most cases prevent two people from changing the same file in parallel. But not allways:
You might have disabled locks in /etc/davfs2/davfs2.conf or
~/.davfs2/davfs2.conf.
The server might not support locks (they are not mandatory).
A bad connection might prevent mount.davfs from refreshing the lock in
time.
Another WebDAV-client might use your lock (that is not too difficult and might
even happen without intention).
FILE OWNER AND PERMISSIONS¶
davfs2 implements Unix permissions for access control. But changing owner and permissions of a file is only local. It is intended as a means for the owner of the file system, to controll whether other local users may acces this file system.FILES¶
- /etc/davfs2/davfs2.conf
- System wide configuration file.
- ~/.davfs2/davfs2.conf
- Configuration file in the users home directory.The user
configuration takes precedence over the system wide configuration. If it
does not exist, mount.davfs will will create a template file.
- /etc/davfs2/secrets
- Holds the credentials for WebDAV servers and the proxy, as
well as decryption passwords for client certificates. The file must be
read-writable by root only.
- ~/.davfs2/secrets
- Holds credentials for WebDAV servers and proxy, as well as
decryption passwords for client certificates. The file must be
read-writable by the owner only. Credentials are first looked up in the
home directory of the mounting user. If not found there the system wide
secrets file is consulted. If no creditentials and passwords are found
they are asked from the user interactively (if not disabled). If the file
does not exist, mount.davfs will will create a template file.
- /etc/davfs2/certs
- You may store trusted server certificates here, that can
not be verified by use of the system wide CA-Certificates. This is useful
when your server uses a selfmade certificate. You must configure the
servercert option in /etc/davfs2/davfs2.conf or
~/.davfs2/davfs2.conf to use it. Certificates must be in PEM
format.
- ~/.davfs2/certs
- You may store trusted server certificates here, that can
not be verified by use of the system wide CA-Certificates. This is useful
when your server uses a selfmade certificate. You must configure the
servercert option in ~/.davfs2/davfs2.conf to use it.
Certificates must be in PEM format.
- /etc/davfs2/certs/private
- To store client certificates. Certificates must be in
PKCS#12 format. You must configure the clientcert option in
/etc/davfs2/davfs2.conf or ~/.davfs2/davfs2.conf to use it.
This directory must be rwx by root only.
- ~/.davfs2/certs/private
- To store client certificates. Certificates must be in
PKCS#12 format. You must configure the clientcert option in
~/.davfs2/davfs2.conf to use it. This directory must be rwx by the
owner only.
- /var/run/mount.davfs
- PID-files of running mount.davfs processes are stored
there. This directory must belong to group davfs2 with write
permissions for the group and the sticky-bit set (mode 1775). The
PID-files are named after the mount point of the file system.
- /var/cache/davfs2
- System wide directory for cached files. Used when the file
system is mounted by root. It must belong do group davfs2 and read,
write and execute bits for group must be set. There is a subdirectory for
every mounted file system. The names of this subdirectories are created
from url, mount point and user name.
- ~/.davfs2/cache
- Cache directory in the mounting users home directory. For every mounted WebDAV resource a subdirectory is created.
ENVIRONMENT¶
- https_proxy http_proxy all_proxy
- If no proxy is defined in the configuration file the value
is taken from this environment variables. The proxy may be given with or
without scheme and with or without port
- no_proxy
- A comma separated list of domain names that shall be
accessed directly. * matches any domain name. A domain name
starting with . (period) matches all subdomains.
EXAMPLES¶
Non root user (e.g. filomena):http://webdav.org/dav /media/dav davfs
noauto,user 0 0
proxy proxy.mycompany.com:8080
proxy.mycompany.com filomena "my
secret"
/media/dav webdav-username password
mount /media/dav
umount /media/dav
mount -t davfs -o
uid=otto,gid=users,mode=775 https://asciigirl.com/webdav /mount/site
mount.davfs -o uid=otto,gid=users,mode=775
http://linux.org.ar/repos/ /dav
BUGS¶
davfs2 does not support links. A davfs2 file system cannot be moved with mount --move.AUTHORS¶
This man page was written by Luciano Bello <luciano@linux.org.ar> for Debian, for version 0.2.3 of davfs2.DAVFS2 HOME¶
http://savannah.nongnu.org/projects/davfs2SEE ALSO¶
umount.davfs(8), davfs2.conf(5), mount(8), umount(8), fstab(5)2009-10-18 | davfs2 |