Bug 62418 - builtin kill -SIG -1 doesn't restrict to current UID
Summary: builtin kill -SIG -1 doesn't restrict to current UID
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: bash
Version: skipjack-beta1
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: wdovlrrw
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks: 61901
TreeView+ depends on / blocked
 
Reported: 2002-03-31 16:43 UTC by Jay Berkenbilt
Modified: 2007-04-18 16:41 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2002-04-11 16:06:03 UTC
Embargoed:


Attachments (Terms of Use)

Description Jay Berkenbilt 2002-03-31 16:43:14 UTC
Description of Problem:

The bash kill builtin appears not to restrict kill -1 to the current uid.

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

bash-2.0.5a-9, 2.05a.0(1)-release

How Reproducible:

always

Steps to Reproduce:
1. start bash as a non-root user
2. bash-2.05a$ kill -HUP -1

Actual Results:

bash: kill: (1) - Operation not permitted

Expected Results:

All process excepting the calling process should receive a hup signal as happens
with other shells, /bin/kill, the kill system call, and the bash kill builtin in
previous versions of bash.

Comment 1 Harald Hoyer 2002-04-05 10:43:32 UTC
bash-2.05a-11 totally screws builtin kill

Comment 2 Bill Nottingham 2002-04-10 20:20:35 UTC
This should be fixed in -12.

Comment 3 Jay Turner 2002-04-11 15:03:39 UTC
OK, this appears to be working lots better with 2.05a-12 . . . wouldn't mind
someone else taking a look to make sure that it's acting correctly though.

Comment 4 Jay Berkenbilt 2002-04-11 16:05:59 UTC
It certainly appears fine to me.  The code I have that depends upon bash's
builtin kill, particularly in the -1 case, works properly with -12 installed.


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