Mailinglist Archive: opensuse (946 mails)

[Richard Creighton <ricreig@xxxxxxxxx>]

On 2010-10-13 Carlos offered the following:

> On Wednesday, 2010-10-13 at 19:47 -0400, Richard Creighton wrote:
> > On 2010-10-13 Carlos offered the following:
> >
> > <snip>
> >
> > > The question remains, how to impede the applet that tells there are
> > > updates pending to not even start. THAT's the main question.
> >
> > <snip>
> >
> > Wouldn't it be just as easy to ask the devs to modify the applet so that
> > it won't run
> > for anyone that isn't 1) UID=0 or 2) GID = a)root  b)wheel  c)trusted
> > d)<some_updater-group-defined-by-root>??? and identified in the config
> > file for the updater or by the dev kinda like the vboxuser has to be set
> > in order to run virtual box....????
>
> Obviously. But that will take years... and we'd like a temporary solution
> while they do.

I would then submit that until that time that a SCRIPT could be written and put 
in 
the login script or autostart scripts that stop/purge such programs according 
to the 
UID/GID per above pending the program(s) doing it as it should.   eg, a 
workaround.   
I'm pretty sure that KDE and Gnome and probably the others have 'autostart' or 
startup scripts/programs that run when a user first logs in that could test the 
list 
of programs it is attempting to startup and proactively skip/kill/ignore the 
ones not 
matching the UID/GID requirements.   Then, IF the root operator gives that user 
extended privileges by making them members of the 'correct' group(s), then the 
associated program(s) can run, ala vbox, updater, etc.

Richard
-- 
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx