1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
|
Required packages for building
==============================
Minimum required packages for building pam_mount from a tarball release:
* C99 compiler
* libHX 4.28 or up
* libmount 2.20 or up
* libpcre 7.0 or up
* libxml 2.6.x or up
* pkg-config 0.19 or up
* choose one of:
* Linux-PAM 0.99.x or up
* SUN-PAM [untested and the last attempt, though successful, is years old]
* BSD PAM [untested and probably not working right now]
Additional required packages for building from (Git) snapshot:
* autoconf 2.59 or up
* automake 1.10 or up
* libtool 1.5.22 or up (older ones might work)
Then, optional packages for building:
* openssl 0.9.8 or up
* libcryptsetup 1.1.2 or up — block-level encryption
Required packages for runtime
-----------------------------
* util-linux 2.20 or up
Suggested packages for runtime
------------------------------
* hxtools
* fd0ssh: to support passing passwords to SSH
* ofl: to support kill-on-logout
Suggested packages for local volumes
------------------------------------
* encfs 1.4 or up — file-level encryption
Suggested packages for remote targets
-------------------------------------
* sshfs — SFTP-over-SSH
* cifs-mount — for CIFS and SMB shares
For configuration validation
----------------------------
* xmllint (libxml2)
Notes for configure
===================
OpenSSL and/or libcryptsetup are optional, to build without them however
you need to explicitly specify ``--without-crypto`` and/or
``--without-libcryptsetup``, respectively.
DTD installation usage
----------------------
Configure pam_mount with ``--with-dtd``.
To validate (assuming the installation prefix was /usr):
.. code-block:: sh
xmllint --nonet --noout --loaddtd --valid --path /usr/share/xml/pam_mount/dtd/pam_mount.conf.xml.dtd /etc/security/pam_mount.conf.xml
|
