compiling pam_mount for FC5

[Roman Maeder]

I couldn't find any rpms for pam_mount-0.12.2 for FC5 and tried to compile
it myself. I didn't get very far, as the "make" output at the end shows.
The file in question is /usr/include/linux/loop.h, which belongs to
glibc-kernheaders-3.0-5.2, so this seems to be up-to-date. Any ideas?

Roman

 gcc -DHAVE_CONFIG_H -I. -I. -I.. -I./../include -I/usr/include/glib-2.0
-I/usr/lib/glib-2.0/include -DG_DISABLE_DEPRECATED -D_LARGEFILE_SOURCE=1
-D_LARGE_FILES -D_FILE_OFFSET_BITS=64 -D_REENTRANT -Wall -Waggregate-return
-Wmissing-declarations -Wmissing-prototypes -Wredundant-decls -Wshadow
-Wstrict-prototypes -Winline -pipe -g -O2 -MT mount.lo -MD -MP
-MF .deps/mount.Tpo -c mount.c  -fPIC -DPIC -o .libs/mount.o
In file included from mount.c:54:
/usr/include/linux/loop.h:31:2: error: #error "Wrong dev_t in loop.h"
mount.c:75: warning: 'struct loop_info64' declared inside parameter list
mount.c:75: warning: its scope is only this definition or declaration, which
is probably not what you want
mount.c: In function 'already_mounted':
mount.c:184: error: storage size of 'loopdev' isn't known
mount.c:184: warning: unused variable 'loopdev'
mount.c: At top level:
mount.c:944: warning: 'struct loop_info64' declared inside parameter list
mount.c:945: error: conflicting types for 'loop_bk'
mount.c:75: error: previous declaration of 'loop_bk' was here
mount.c:951:6: error: #error
-------------------------------------------------------------------
mount.c:952:6: error: #error Your userspace kernel headers
(/usr/include/linux/) are out of date
mount.c:953:6: error: #error This is NOT a pam-mount bug, but one of your
distribution.
mount.c:954:6: error: #error
-------------------------------------------------------------------
mount.c: In function 'loop_bk':
mount.c:956: error: 'LOOP_GET_STATUS64' undeclared (first use in this
function)
mount.c:956: error: (Each undeclared identifier is reported only once
mount.c:956: error: for each function it appears in.)
mount.c:961: error: dereferencing pointer to incomplete type
make[2]: *** [mount.lo] Error 1
make[2]: Leaving directory `/usr/local/src/pam_mount-0.12.2/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/local/src/pam_mount-0.12.2'
make: *** [all] Error 2

[Craig McLean]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Roman Maeder wrote:
>  I couldn't find any rpms for pam_mount-0.12.2 for FC5 and tried
> to compile
>  it myself. I didn't get very far, as the "make" output at the end shows.
>  The file in question is /usr/include/linux/loop.h, which belongs to
>  glibc-kernheaders-3.0-5.2, so this seems to be up-to-date. Any ideas?
>  
>  Roman 
[snip]

Roman,

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=174190

FYI, pam_mount-0.9.25 should build ok. It's what I'm using here.

C.

- --
Craig McLean		http://fukka.co.uk
craig(a)fukka.co.uk	Where the fun never starts
	Powered by FreeBSD, and GIN!
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2.2 (GNU/Linux)
>
> iD8DBQFELZsDMDDagS2VwJ4RAnJUAJ47MstR3RczqS0uoIuBpvV3pch8LQCeLH9l
> 3d6cEmUbohLKMjRheq877sE=
> =sGTj
> -----END PGP SIGNATURE-----

[Roman Maeder]

Craig McLean wrote:

>  ...
>  https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=174190
>  
>  FYI, pam_mount-0.9.25 should build ok. It's what I'm using here.
>   
today pam_mount-0.13.0 was released, and it comes with a
pam_mount-0.13.0.i586.rpm on sourceforge. However this was linked against
openssl-0.9.7, which is not installed in FC5. So I grabbed openssl097a,
which contains these versions, but not the symlinks; after creating them
in /lib
libcrypto.so.0.9.7 -> libcrypto.so.0.9.7a*
libssl.so.0.9.7 -> libssl.so.0.9.7a*
I was able to use pam_mount.

It's not easy. The pam_mount.conf file has this config for the crypt
filesystem:

cryptmount /bin/mount -t crypt "%(before=\"-o\" OPTIONS)" %(VOLUME)
%(MNTPT)

but the FC5 mount program does not understand the "crypt" fs type (is there
a mount that does? I thought this was an open issue with dm-crypt). So I
installed the mount.crypt script that comes with pam_mount and changed the
config to

cryptmount /bin/mount.crypt %(VOLUME) %(MNTPT) -o %(OPTIONS)

and after hacking the login,rlogin,remote pam.d configs I am now able to
have the homedir mounted in a test setting. I created a test user "bozo"
and prepared an encrypted plain-file container and use it with this line in
pam_mount.conf:

volume bozo crypt - /var/cryptohome /bozo loop,fstype=ext3 - -

There is one remaining problem. The mount.crypt script tries to come up with
a suitable mapper device name from the target of the loopback device it
creates (in this case it should be _var_cryptohome), and the code looks
like this:

DMDEVICE=` "$LOSETUP" "$DEVICE" 2>/dev/null | sed -n '/(.+)/ {
s/.*(//;
s/).*//; p;}'`;

the FC5 losetup generates output such as

/dev/loop0: [0303]:97744 (/var/cryptohome)

and I can't figure out why the address pattern /(.+)/ doesn't match (the sed
generates no output), so ended up deleting it and use

DMDEVICE=` "$LOSETUP" "$DEVICE" 2>/dev/null | sed -n '{
s/.*(//; s/).*//;
p;}'`;

the name is important because pam_mount uses it to check whether the
filesystem has already been mounted.

Roman