Bug 180342 - sudo prompts for passwd when NOPASSWD is used in conjunction with Host_Alias
Summary: sudo prompts for passwd when NOPASSWD is used in conjunction with Host_Alias
Keywords:
Status: CLOSED DUPLICATE of bug 170023
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: sudo
Version: 4.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Karel Zak
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-02-07 14:09 UTC by Harri Sylvander
Modified: 2007-11-30 22:07 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-07 15:30:47 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Harri Sylvander 2006-02-07 14:09:05 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20060130 Red Hat/1.0.7-1.4.3 Firefox/1.0.7

Description of problem:
NOPASSWD does not work when used in combination with Host_Aliases. Defining a Host_Alias for multiple networks breaks functionality:

/etc/sudoers 
---snip---
Host_Alias TEST_NETS = \
                       192.168.1.0, \
                       192.168.2.0, \
                       192.168.3.0

Cmnd_Alias TEST_CMDS = /bin/touch /tmp/test
Defaults        timestamp_timeout=0, !lecture
nobody TEST_NETS = NOPASSWD: TEST_CMDS
---snip---

Running sudo will prompt for password.


Version-Release number of selected component (if applicable):
sudo-1.6.7p5-30.1.1

How reproducible:
Always

Steps to Reproduce:
1. Add multiple networks in a Host_Alias and use NOPASSWD(see sudoers example in description)
2. Run

     $ sudo /bin/touch /tmp/test 


Actual Results:  User will be prompted for password.

Expected Results:  A file /tmp/test should've been created with root:root owner w/o password prompt

Additional info:

Tried grabbing sudo source from http://www.courtesan.com/sudo/ and compiling without any extram params(./configure; make; make install). Using same /etc/sudoers produced expected result.

Comment 1 Karel Zak 2006-02-07 15:30:47 UTC

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


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