Bug 431 – sudo -s in 1.7.4 with HAVE_PAM forks and waits but child bash hung after suspend

Bug 431 - sudo -s in 1.7.4 with HAVE_PAM forks and waits but child bash hung after suspend


Summary:	sudo -s in 1.7.4 with HAVE_PAM forks and waits but child bash hung after suspend

Status:	RESOLVED FIXED

Product:	Sudo
Classification:	Unclassified
Component:	Sudo
Version:	1.7.4
Hardware:	All Linux

Importance:	low normal
Assigned To:	Todd C. Miller

URL:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2010-08-24 00:59 MDT by SBertilson
Modified:	2010-09-14 16:41 MDT (History)
CC List:	0 users

See Also:

Attachments
Patch to pass on SIGCONT when sudo resumes after suspend (510 bytes, application/octet-stream) 2010-08-24 08:44 MDT, Todd C. Miller	Details
Add an attachment (proposed patch, testcase, etc.)

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

Description SBertilson 2010-08-24 00:59:22 MDT

HAVE_PAM activates CMND_WAIT which causes a fork/exec rather than a pure exec.  When I "suspend" the resulting bash session and try "fg" to bring it back, the sudo continues, but the bash remains stopped.  If I SIGCONT the bash, it works fine until the next suspend.

Comment 1 Todd C. Miller 2010-08-24 08:44:41 MDT

Created attachment 287 [details]
Patch to pass on SIGCONT when sudo resumes after suspend

I've attached a patch which fixes this.  It will be part of sudo 1.7.5.

Comment 2 Todd C. Miller 2010-09-14 16:41:21 MDT

Fixed in sudo 1.7.4p4