Crash in pam_sm_authenticate

Bug #1413559 reported by Milan Bouchet-Valat
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
eCryptfs
New
Undecided
Unassigned
Fedora
Fix Released
Undecided

Bug Description

This crash has been experienced by several people on Fedora 21 [1]. I've personally seen it with ecryptfs-utils 103.

I've tried reporting it to GNOME [2], and here's what Ray Strode said:
"this looks like some sort of bug in pam_ecryptfs not a bug in gdm. My guess is
ecryptfs uses the typed in password to decrypt the fs, but with fingerprint
login, there's not password to decrypt with. you probably need to disable the
fingerprint login and/or take pam_ecryptfs out of your fingerprint
authentication stack."

Note that I'm not using the fingerprint at all, and anyway a crash is an incorrect behavior.

1: https://bugzilla.redhat.com/show_bug.cgi?id=1184645
2: https://bugzilla.gnome.org/show_bug.cgi?id=726735

#0 strlen () at ../sysdeps/x86_64/strlen.S:106
No locals.
#1 0x00007f473c67211e in __GI___strdup (s=0x0) at strdup.c:41
        len = <optimized out>
        new = <optimized out>
#2 0x00007f4731d2df63 in pam_sm_authenticate (pamh=0x7f473fb173d0, flags=<optimized out>, argc=1, argv=0x7f473fb14e10) at pam_ecryptfs.c:161
        salt_hex = '\000' <repeats 15 times>
        private_mnt = 0x7f473fb31660 "/home/autarch/Private"
        rc = 0
        epd = 0x7f473fb30990
        __FUNCTION__ = "pam_sm_authenticate"
#3 0x00007f473cde9fd2 in _pam_dispatch_aux (use_cached_chain=<optimized out>, resumed=<optimized out>, h=<optimized out>, flags=0, pamh=0x7f473fb173d0) at pam_dispatch.c:110
        retval = <optimized out>
        cached_retval = <optimized out>
        action = <optimized out>
        depth = 7
        status = 7
        prev_level = <optimized out>
        stack_level = <optimized out>
        impression = -1
        skip_depth = 0
        substates = 0x7f473fb2ee10
#4 _pam_dispatch (pamh=pamh@entry=0x7f473fb173d0, flags=0, choice=choice@entry=1) at pam_dispatch.c:424
        h = <optimized out>
        retval = <optimized out>
        use_cached_chain = <optimized out>
        resumed = <optimized out>
#5 0x00007f473cde9890 in pam_authenticate (pamh=0x7f473fb173d0, flags=<optimized out>) at pam_auth.c:34
        retval = <optimized out>
#6 0x00007f473e19fd5b in gdm_session_worker_authenticate_user (error=0x7fff956b1420, password_is_required=0, worker=0x7f473faeb140) at gdm-session-worker.c:1176
        error_code = <optimized out>
        authentication_flags = 0
#7 do_authenticate (worker=0x7f473faeb140) at gdm-session-worker.c:2425
        error = 0x0
#8 state_change_idle (worker=0x7f473faeb140) at gdm-session-worker.c:2638
        new_state = <optimized out>
        __FUNCTION__ = "state_change_idle"
#9 0x00007f473d6b0aeb in g_main_dispatch (context=0x7f473fae9150) at gmain.c:3111
        dispatch = 0x7f473d6ad630 <g_idle_dispatch>
        prev_source = 0x0
        was_in_call = 0
        user_data = 0x7f473faeb140
        callback = 0x7f473e19fbe0 <state_change_idle>
        cb_funcs = 0x7f473d99e8c0 <g_source_callback_funcs>
        cb_data = 0x7f473fb2ede0
        need_destroy = <optimized out>
        source = 0x7f473fb2cca0
        current = 0x7f473fafa070
        i = 0
#10 g_main_context_dispatch (context=context@entry=0x7f473fae9150) at gmain.c:3710
No locals.
#11 0x00007f473d6b0e88 in g_main_context_iterate (context=0x7f473fae9150, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3781
        max_priority = 200
        timeout = 0
        some_ready = 1
        nfds = <optimized out>
        allocated_nfds = 2
        fds = 0x7f473fb07a30
#12 0x00007f473d6b11b2 in g_main_loop_run (loop=0x7f473fb07a50) at gmain.c:3975
        __FUNCTION__ = "g_main_loop_run"
#13 0x00007f473e1971b0 in main (argc=1, argv=0x7fff956b1758) at session-worker-main.c:132
        main_loop = 0x7f473fb07a50
        context = <optimized out>
        worker = 0x7f473faeb140
        address = <optimized out>
        is_for_reauth = <optimized out>
        entries = {{long_name = 0x0, short_name = 0 '\000', flags = 0, arg = G_OPTION_ARG_NONE, arg_data = 0x0, description = 0x0, arg_description = 0x0}}

Revision history for this message
In , autarch (autarch-redhat-bugs) wrote :

Version-Release number of selected component:
gdm-3.14.1-2.fc21

Additional info:
reporter: libreport-2.3.0
backtrace_rating: 4
cmdline: 'gdm-session-worker [pam/gdm-password]'
crash_function: strlen
executable: /usr/libexec/gdm-session-worker
kernel: 3.18.3-201.fc21.x86_64
runlevel: N 5
type: CCpp
uid: 0

Truncated backtrace:
Thread no. 1 (9 frames)
 #0 strlen at ../sysdeps/x86_64/strlen.S:106
 #1 __strdup at strdup.c:41
 #2 pam_sm_authenticate at pam_ecryptfs.c:161
 #3 _pam_dispatch_aux at pam_dispatch.c:110
 #4 _pam_dispatch at pam_dispatch.c:424
 #5 pam_authenticate at pam_auth.c:34
 #6 gdm_session_worker_authenticate_user at gdm-session-worker.c:1176
 #7 do_authenticate at gdm-session-worker.c:2425
 #8 state_change_idle at gdm-session-worker.c:2638

Potential duplicate: bug 989653

Revision history for this message
In , autarch (autarch-redhat-bugs) wrote :

Created attachment 982527
File: backtrace

Revision history for this message
In , autarch (autarch-redhat-bugs) wrote :

Created attachment 982528
File: cgroup

Revision history for this message
In , autarch (autarch-redhat-bugs) wrote :

Created attachment 982529
File: core_backtrace

Revision history for this message
In , autarch (autarch-redhat-bugs) wrote :

Created attachment 982530
File: dso_list

Revision history for this message
In , autarch (autarch-redhat-bugs) wrote :

Created attachment 982531
File: environ

Revision history for this message
In , autarch (autarch-redhat-bugs) wrote :

Created attachment 982532
File: exploitable

Revision history for this message
In , autarch (autarch-redhat-bugs) wrote :

Created attachment 982533
File: limits

Revision history for this message
In , autarch (autarch-redhat-bugs) wrote :

Created attachment 982534
File: maps

Revision history for this message
In , autarch (autarch-redhat-bugs) wrote :

Created attachment 982535
File: open_fds

Revision history for this message
In , autarch (autarch-redhat-bugs) wrote :

Created attachment 982536
File: proc_pid_status

Revision history for this message
In , autarch (autarch-redhat-bugs) wrote :

Created attachment 982537
File: var_log_messages

Revision history for this message
In , Milan (milan-redhat-bugs) wrote :

*** Bug 989653 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

ecryptfs-utils-103-7.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/ecryptfs-utils-103-7.fc21

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

Package ecryptfs-utils-103-7.fc21:
* should fix your issue,
* was pushed to the Fedora 21 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing ecryptfs-utils-103-7.fc21'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2015-1213/ecryptfs-utils-103-7.fc21
then log in and leave karma (feedback).

Revision history for this message
In , Milan (milan-redhat-bugs) wrote :

I'm using ecryptfs-utils-103-7 and I just got the same crash on login. (Or at least a very similar one, see Bug 989653). I see the crash everytime I authenticate.

Revision history for this message
In , Michal (michal-redhat-bugs) wrote :

Milan: If it crashes, I will need new backtrace. The easiest way should be to report it as a new bug from abrt.

Revision history for this message
In , Milan (milan-redhat-bugs) wrote :

I tried, but ABRT considered it was a duplicate of this bug.

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

ecryptfs-utils-103-7.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.

Changed in fedora:
importance: Unknown → Undecided
status: Unknown → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.