Sorry, sent to the wrong list. -------- Weitergeleitete Nachricht -------- Von: Michael 'Mickey' Lauer <mic...@vanille-media.de> Reply-to: "freesmartphone.org API standards" <smartphones-standa...@linuxtogo.org> An: smartphones-standa...@linuxtogo.org <smartphones-standa...@linuxtogo.org> Betreff: Re: Default FSO system group Datum: Wed, 04 Mar 2009 18:02:46 +0100
I don't have any objections to increasing the granularity of access control, the fact that [in OE] everything runs under the same user and all services share one dbus permission file is merely due to a mixture of not enough time and being lazy. It was -- however -- always my plan to have this fine granular control, that's why I decided to split the FSO architecture into individual subsystems [and plugins] in the first place. More over, once we move from the Python implementation to another reference implementation, the individual subsystem will be seperate processes again. Three random examples to make it clear what I'd like to see: 1.) Everyone being denied to access the serial device node except ogsmd, 2.) Everyone but ophoned and opimd being denied to call ogsmd, 3.) Everying but ousaged being forbidden to call any frameworkd's object org.freesmartphone.Resource, _if_ ousaged is present in the system. Some of these might be a bit too extreme, we need a couple of iterations here. Bottom line though is that I'd appreciate patches going into this direction. Cheers, -- :M: _______________________________________________ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
