Package: libpam-mount
Version: 2.0-1
Severity: normal
When I login on the console under a user for whom a tmpfs volume should
be mounted as specified in the attached pam_mount.conf.xml file, I get the
message
pam_mount(rdconf1.c:1325): Volume none: consider specifying the fskeyhash
in between the login prompt and the motd and then again between the motd
and the actual command prompt.
This message goes away if I add fskeyhash="md5" to the volume
definition. This doesn't seem to make much sense however, since the
volume is not encrypted. Should this recommendation be appearing for a
tmpfs mount?
Kevin
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (600, 'unstable'), (500, 'testing'), (400, 'stable'), (300,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.33.2003 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) (ignored: LC_ALL set to
en_GB)
Shell: /bin/sh linked to /bin/dash
Versions of packages libpam-mount depends on:
ii libc6 2.10.2-7 Embedded GNU C Library: Shared lib
ii libcryptsetup1 2:1.1.0-2.1 libcryptsetup shared library
ii libhx22 3.4-1 A library providing queue, tree, I
ii libpam-runtime 1.1.1-3 Runtime support for the PAM librar
ii libpam0g 1.1.1-3 Pluggable Authentication Modules l
ii libssl0.9.8 0.9.8n-1 SSL shared libraries
ii libxml2 2.7.7.dfsg-2 GNOME XML library
ii mount 2.16.2-0 Tools for mounting and manipulatin
libpam-mount recommends no packages.
Versions of packages libpam-mount suggests:
pn davfs2 <none> (no description available)
ii fuse-utils 2.8.1-1.2 Filesystem in USErspace (utilities
ii lsof 4.81.dfsg.1-1 List open files
pn ncpfs <none> (no description available)
ii openssl 0.9.8n-1 Secure Socket Layer (SSL) binary a
ii psmisc 22.11-1 utilities that use the proc file s
ii smbfs 2:4.1-1 Common Internet File System utilit
ii sshfs 2.2-1 filesystem client based on SSH Fil
pn tc-utils <none> (no description available)
ii xfsprogs 3.1.1 Utilities for managing the XFS fil
-- Configuration Files:
/etc/security/pam_mount.conf.xml changed:
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE pam_mount SYSTEM "pam_mount.conf.xml.dtd">
<!--
See pam_mount.conf(5) for a description.
-->
<pam_mount>
<!-- debug should come before everything else,
since this file is still processed in a single pass
from top-to-bottom -->
<debug enable="0" />
<volume sgrp="tmpfs" fstype="tmpfs" path="none" mountpoint="~/tmp"
options="size=2G,uid=%(USER),mode=0700" fskeyhash="md5" />
<!-- Volume definitions -->
<!-- pam_mount parameters: General tunables -->
<!--
<luserconf name=".pam_mount.conf.xml" />
-->
<!-- Note that commenting out mntoptions will give you the defaults.
You will need to explicitly initialize it with the empty string
to reset the defaults to nothing. -->
<mntoptions
allow="nosuid,nodev,loop,encryption,fsck,nonempty,allow_root,allow_other" />
<!--
<mntoptions deny="suid,dev" />
<mntoptions allow="*" />
<mntoptions deny="*" />
-->
<mntoptions require="nosuid,nodev" />
<path>/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin</path>
<logout wait="0" hup="0" term="0" kill="0" />
<!-- pam_mount parameters: Volume-related -->
<mkmountpoint enable="1" remove="true" />
</pam_mount>
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
