Bug 1268958 - sudo - cmnd_no_wait can cause child processes to ignore SIGPIPE
Summary: sudo - cmnd_no_wait can cause child processes to ignore SIGPIPE
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: sudo
Version: 7.1
Hardware: Unspecified
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Daniel Kopeček
QA Contact: Stefan Kremen
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-05 18:15 UTC by Dalibor Pospíšil
Modified: 2016-11-03 20:31 UTC (History)
3 users (show)

Fixed In Version: sudo-1.8.6p7-18.el7
Doc Type: Bug Fix
Doc Text:
Clone Of: 1094548
Environment:
Last Closed: 2016-11-03 20:31:50 UTC
Target Upstream Version:


Attachments (Terms of Use)
proposed patch (554 bytes, patch)
2016-05-10 09:16 UTC, Daniel Kopeček
no flags Details | Diff


Links
System ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:2593 normal SHIPPED_LIVE Low: sudo security, bug fix, and enhancement update 2016-11-03 12:10:56 UTC

Description Dalibor Pospíšil 2015-10-05 18:15:02 UTC
+++ This bug was initially created as a clone of Bug #1094548 +++

Description of problem:

The bug 1094548 appears to be present also on RHEL7.

Version-Release number of selected component (if applicable):
sudo-1.8.6p7-13.el7


How reproducible:

Always


Steps to Reproduce:

1. Set "Defaults cmnd_no_wait" in /etc/sudoers

2. Run the following command all together:

    $ sudo -k; sudo bash -c "yes | fold | head -n1"

   Note: As mentioned below, the sudo -k is important to ensure there
         is an out of date cache. [1]

Actual results:

 Sudo ignores SIGPIPE somewhere in the authentication stack, perhaps
 in src/tgetpass.c.  Thus the command hangs.


Expected results:

  The chain executed by sudo should not hang in these cases.

Comment 3 Daniel Kopeček 2016-05-10 09:16:55 UTC
Created attachment 1155628 [details]
proposed patch

Comment 7 errata-xmlrpc 2016-11-03 20:31:50 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/RHSA-2016-2593.html


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