[yast-devel] messing with /etc/PolicyKit/PolicyKit.conf
Hi, jsrain is trying to get WebYaST running from git. In http://en.opensuse.org/YaST/Web/Development#Setup_permissions it says to edit PolicyKit.conf. Will this not confuse the permission handler? AFAIK it checks for explicit permissions only. I think there is a helper script that sets up the explicit permissions, right? How to call it? Also, at some time our scripts used to mess with PolicyKit.conf. RPMs must not do that. Is that removed by now? -- Martin Vidner, YaST developer http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
On Fri, Jul 10, 2009 at 09:40:00AM +0200, Martin Vidner wrote:
Hi,
jsrain is trying to get WebYaST running from git. In http://en.opensuse.org/YaST/Web/Development#Setup_permissions it says to edit PolicyKit.conf. Will this not confuse the permission handler? AFAIK it checks for explicit permissions only. I think there is a helper script that sets up the explicit permissions, right? How to call it?
Also, at some time our scripts used to mess with PolicyKit.conf. RPMs must not do that. Is that removed by now?
Ludwig Nussel is the guy to ask. I have forwarded your mail. Ciao, Marcus -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Marcus Meissner schrieb:
On Fri, Jul 10, 2009 at 09:40:00AM +0200, Martin Vidner wrote:
Hi,
jsrain is trying to get WebYaST running from git. In http://en.opensuse.org/YaST/Web/Development#Setup_permissions it says to edit PolicyKit.conf. Will this not confuse the permission handler? AFAIK it checks for explicit permissions only. I think there is a helper script that sets up the explicit permissions, right? How to call it?
The permissions will be set via polkit-auth. Patching PolicyKit.conf has been a workaround only. ( Perhaps just for developping)
Also, at some time our scripts used to mess with PolicyKit.conf. RPMs must not do that. Is that removed by now?
This was in former version of the rest-service ( RPM postinstall) But the latest version does not have this PolicyKit.conf changes anymore.
Greetings Stefan
Ludwig Nussel is the guy to ask. I have forwarded your mail.
Ciao, Marcus
-- ******************************************************************************* Stefan Schubert SUSE LINUX GmbH - Maxfeldstrasse 5 - D-90409 Nuernberg, Germany e-mail: schubi@suse.de ------------------------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
On Fri, Jul 10, 2009 at 11:03:56AM +0200, Stefan Schubert wrote:
The permissions will be set via polkit-auth. Patching PolicyKit.conf has been a workaround only. ( Perhaps just for developping)
Yes, polkit-auth, but that is the low level tool for it. I found this: ruby rest-service/dist/policyKit-rights.rb --user $USER --action grant Where USER is set by your shell to yourself and it works for the case where you run the rest service as yourself (the RPM runs it as yastws).
Also, at some time our scripts used to mess with PolicyKit.conf. RPMs must not do that. Is that removed by now?
This was in former version of the rest-service ( RPM postinstall) But the latest version does not have this PolicyKit.conf changes anymore.
Good, thanks. -- Martin Vidner, YaST developer http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
participants (3)
-
Marcus Meissner -
Martin Vidner -
Stefan Schubert