Bug 1198259

Summary: The vsftpd hangs in a SIGCHLD handler when the pam_exec.so is used in pam.d configuration
Product: Red Hat Enterprise Linux 7 Reporter: Dalibor Pospíšil <dapospis>
Component: vsftpdAssignee: Martin Osvald 🛹 <mosvald>
Status: CLOSED ERRATA QA Contact: Dalibor Pospíšil <dapospis>
Severity: high Docs Contact:
Priority: high    
Version: 7.1CC: ksrot, mosvald
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1092877 Environment:
Last Closed: 2015-11-19 14:48:56 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1205796    

Description Dalibor Pospíšil 2015-03-03 16:38:32 UTC 
The issue seems to appear also on RHEL7.
+++ This bug was initially created as a clone of Bug #1092877 +++

Description of problem:
The vsftpd hangs when the pam_exec.so is added to the /etc/pam.d/vsftpd.

---------------------------------------------
...
...
session    include	password-auth
session    optional     pam_exec.so /bin/echo
---------------------------------------------

Version-Release number of selected component (if applicable):
vsftpd-3.0.2-9.el7

How reproducible:
always

Steps to Reproduce:
1. add pam_exec.so calling echo to /etc/pam.d/vsftpd
2. add session_support=YES to /etc/vsftpd/vsftpd.conf
3. restart vsftpd
4. connect with a client to the vsftpd
5. login and send e.g. ls command

Actual results:
The vsftpd hangs in SIGCHLD handler

Expected results:
The vsftpd will work as intended.
Comment 7 errata-xmlrpc 2015-11-19 14:48:56 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2015-2446.html