Bug 176000 - mahjongg doesn't start because its setuid root
Summary: mahjongg doesn't start because its setuid root
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-games
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-12-17 04:48 UTC by Jef Spaleta
Modified: 2007-11-30 22:11 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-16 05:25:33 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jef Spaleta 2005-12-17 04:48:41 UTC
Description of problem:
>mahjongg

(mahjongg:4715): Gtk-WARNING **: This process is currently running setuid or setgid.
This is not a supported use of GTK+. You must create a helper
program instead. For further details, see:

    http://www.gtk.org/setuid.html


Version-Release number of selected component (if applicable):
gnome-games-2.13.3-1

Expected results:
mahjongg should probably not be setuid root any longer since gtk seems to no
longer allow that.


-jef

Comment 1 Jef Spaleta 2005-12-17 04:53:51 UTC
This affects several games in gnome-games
mahjongg
gnomines
same-gnome
glines

all have the same error about setuid

without mahjongg or gnomines working how am I suppose to get through my workday?

-jef


Comment 2 Warren Togami 2005-12-17 04:55:36 UTC
Security implications, advice would be appreciated.

WHY would these things be setuid?

Comment 3 Bill Nottingham 2005-12-17 05:13:10 UTC
They're setgid games, for writing score files. Have been that way for a while...

Comment 4 Jef Spaleta 2005-12-17 05:36:26 UTC
appearently gtk no longer likey the setgid


Comment 5 Mark J. Cox 2005-12-19 10:53:37 UTC
See http://bugzilla.ubuntu.com/show_bug.cgi?id=19668#c8 for an explanation of
why these games have started being blocked (due to an upstream change in the games).

Comment 6 Mark J. Cox 2005-12-19 10:56:13 UTC
Also http://lwn.net/Articles/156888/ which documents the new scores API behaviour


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