Bug 920538 - ssh-agent blocks SIGTERM when started via kdm and pam_ssh
Summary: ssh-agent blocks SIGTERM when started via kdm and pam_ssh
Keywords:
Status: CLOSED DUPLICATE of bug 913820
Alias: None
Product: Fedora
Classification: Fedora
Component: kde-workspace
Version: 18
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-12 10:28 UTC by f.pasquarelli
Modified: 2013-03-12 13:11 UTC (History)
15 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-03-12 13:11:53 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Novell 727246 0 None None None Never

Description f.pasquarelli 2013-03-12 10:28:56 UTC
Description of problem:
When pam_ssh is used to authenticate for kdm login into KDE session and start
ssh-agent, ssh-agent keeps running after the session is finished and cannot be
killed by TERM signal.

This is because kdm blocks TERM signal when calling pam_ssh_code and this
signal mask is inherited by ssh-agent. As ssh-agent blocks SIGTERM, it is not
finished upon logout from KDE session.


Version-Release number of selected component (if applicable): pam_ssh-1.97-11


How reproducible:


Steps to Reproduce:
1. graphicl login with kdm authenticating with passphrase
2. logout
  
Actual results: the ssh_agent process is not killed


Expected results: all user processes should be killed


Additional info: see https://bugzilla.novell.com/show_bug.cgi?id=727246 for a similar report where patches are proposed

Comment 1 Dmitry Butskoy 2013-03-12 12:25:12 UTC
It seems there is no such an issue with gdm (Gnome display manager).

IOW, it looks like something KDM-specific.

Does Kdm have any solution for such issues? Besides pam_ssh, some other pam modules might invoke programs at startup (keyrings, mounts, etc?), hence it is more a common problem rather than an pam_ssh only.

Comment 2 Martin Bříza 2013-03-12 13:11:53 UTC

*** This bug has been marked as a duplicate of bug 913820 ***


Note You need to log in before you can comment on or make changes to this bug.