I've recently upgraded from pam_mount 2.4 to 2.11. Unfortunately, in this version (and also in 2.10), I'm not able to mount a "large" image file: > ls -lh /.homes/home.jasper.vol -rw-r--r-- 1 root root 9.8G Oct 4 21:17 /.homes/home.jasper.vol > mount.crypt /.homes/home.jasper.vol /mnt mount.crypt: stat /.homes/home.jasper.vol: Value too large for defined data type which to me seems to indicate that mount.crypt was comiled with incorrect options for large file support. Needless to say this makes working with encrypted home directories quite cumbersome... Manually mounting the volume, using losetup, cryptsetup and mount works fine, so this looks like a problem with recent pam_mount. Also, the previous (2.4) version worked without a problem - unfortunately, it cannot be compiled any more against a recent system. That said, I've noticed that after the configure run for pam_mount, the _FILE_OFFSET_BITS=64 compiler define (which I think is needed for large file support) is not used in the resulting Makefile (which is different from 2.4), so it seems it is stripped off somewhere - I'm not a autoconf guru, at all, though. Please let me know if you require further information.
contacted upstream, fixed in 2.12.
2.12 works correctly (for me)
