I upgraded to 1.30 yesterday, and it triggers segfault in pam, apparently
when user non configured to use pam_mount service is concerned, as root.
For instance, su triggers this:
#0 strlen () at ../sysdeps/x86_64/strlen.S:31
No locals.
#1 0x00007f5a40fdd5d1 in pam_sm_open_session (pamh=0x1e19540, flags=<value
optimized out>, argc=<value optimized out>, argv=<value optimized out>) at
pam_mount.c:599
ret = <value optimized out>
krb5 = <value optimized out>
system_authtok = 0x0
tmp = (const void *) 0x1e19540
getval = <value optimized out>
__PRETTY_FUNCTION__ = "pam_sm_open_session"
#2 0x00007f5a4281fbee in _pam_dispatch (pamh=0x1e19540, flags=<value
optimized out>, choice=<value optimized out>) at pam_dispatch.c:110
h = (struct handler *) 0x1e231a0
retval = <value optimized out>
use_cached_chain = <value optimized out>
resumed = <value optimized out>
#3 0x00007f5a42823d78 in pam_open_session (pamh=0x0, flags=0) at
pam_session.c:23
retval = <value optimized out>
#4 0x000000000040201c in run_shell (shell=0x1e21360 "/bin/bash",
command=0x0, additional_args=0x7fff6f918ff0, n_additional_args=0, pw=<value
optimized out>) at su.c:454
n_args = <value optimized out>
argno = <value optimized out>
ourset = {__val = {1, 0, 0, 31593376, 2, 31593376, 31593312, 4215331,
140025637461248, 4215243, 140735065198160, 140025634155006, 327697123411,
140025634421034, 16, 140025634154953}}
status = 0
#5 0x00000000004029b3 in main (argc=<value optimized out>,
argv=0x7fff6f918fe8) at su.c:742
optc = <value optimized out>
new_user = 0x4051cb "root"
command = 0x0
shell = 0x1e21360 "/bin/bash"
pw = <value optimized out>
pw_copy = {pw_name = 0x1e194c0 "root", pw_passwd = 0x1e194e0 "x",
pw_uid = 0, pw_gid = 0, pw_gecos = 0x1e19087 "root", pw_dir = 0x1e19500
"/root", pw_shell = 0x1e19520 "/bin/bash"}
However, logging as 'guillaume' user works as expected.
Here is my pam_mount configuration:
<pam_mount>
<volume user="guillaume" fstype="crypt" path="/dev/sda7" mountpoint="/home"
cipher="aes-cbc-essiv:sha256"/>
<debug enable="0" />
<mntoptions
allow="nosuid,nodev,loop,encryption,fsck,nonempty,allow_root,allow_other"
/>
<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" />
<mkmountpoint enable="0" remove="true" />
</pam_mount>
Jan Engelhardt
pam_mount
pam_mount
Public
|
Date: 2009-09-02 19:20 Indeed, version 1.31 fixes the issues.Thanks :) |
|
Date: 2009-09-01 21:31 Does this patch help? |
|
Date: 2009-09-01 19:29 I forgot: this happened with libHX 3.0. I updated to libHX 3.0.1, it |
| Field | Old Value | Date | By |
|---|---|---|---|
| status_id | Open | 2009-09-02 19:22 | jengelh |
| close_date | - | 2009-09-02 19:22 | jengelh |
| status_id | Pending | 2009-09-02 19:20 | guillomovitch |
| close_date | 2009-09-01 21:31 | 2009-09-02 19:20 | guillomovitch |
| resolution_id | None | 2009-09-01 21:31 | jengelh |
| close_date | - | 2009-09-01 21:31 | jengelh |
| status_id | Open | 2009-09-01 21:31 | jengelh |