Mailinglist Archive: yast-devel (95 mails)

[Stefan Schubert <schubi@xxxxxxx>]

Martin Vidner schrieb:
> On Mon, Jun 15, 2009 at 01:14:08PM +0200, Stefan Schubert wrote:
>   
> > Martin Vidner schrieb:
> >     
> > > I think that it is a futile attempt to overcome the initial problem
> > > of having too many permissions to deal with.
> > >   
> > >       
> > Thats my main aim to reduce the amount of permissions :-)
> >     
> > > How about removing them instead? That means not having the complete
> > > "API" of YaST accessible via DBus, but it is not a real API anyway.
> > > Instead, we should build the API to fit the permissions.
> > >
> > >   
> > >       
> > My intention is to have one permission file for the REST AND the DBUS 
> > interface.
> > Thats why I would like to use this tree structure in order to make it 
> > simple.
> >     
>
>   
Hey, I am older than you. So please forgive me if takes a little bit 
longer until
I am understanding or having an overview :-)
> Can't you see? You are not removing them, only hiding.
>   
Yes, "hiding" that is the point and that's why we should use the tree 
structure and
showing not all sub branches (default) but almost root branches like 
language/get
language/set only. If the admin is interested in more details he can 
show the subtrees too.
(The question if granulated permissions are need at all in the language 
module has
already been discussed).

I know, that is a compromise but it prevents us for defining a new 
configuration file
with which the "hiding rules" are defined.

> It is good if you want to unify the permission files for the two
> layers.
> But it is the wrong way around if you take the existing non-API and
> create the permissions from that, because that floods the admin with
> detail, which is not well designed anyway.
>   
Fully agree. But here comes the question why it is not well designed and 
why
there is so much different between the YaST-DBUS interface and the 
YaST-REST interface
which is described in the policies too ?
From my point of view the YaST-Webservice should only be a wrapper 
which transforms
the YaST-DBUS interface to the YaST-REST interface automatically.
Due the fact that DBUS already provides tools like interspection it 
should not be a big problem
to make this automatically.
Currently it is not possible cause not all YaST modules provides the 
YaST-DBUS interface
( state one month ago :-) ). So we are wrapping via SCR calls now.

Please inform me if I am still on the wrong path ;-)

Greetings
Stefan



--
*******************************************************************************
Stefan Schubert
SUSE LINUX GmbH - Maxfeldstrasse 5 - D-90409 Nuernberg, Germany
e-mail: schubi@xxxxxxx
-------------------------------------------------------------------------------
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)


--
To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: yast-devel+help@xxxxxxxxxxxx