> -----Original Message----- > From: [email protected] [mailto:[email protected]] On > Behalf Of Rees, Kevron > Sent: Friday, January 24, 2014 12:57 PM > To: Clark, Joel > Cc: [email protected] > Subject: Re: [Dev] kdbus-enabled Tizen 3 update > > FYI, while trying to gbs build the kdbus-bus from the kdbus-integration > branch I get: > > error: Invalid upstream treeish upstream/0.5 > > Looks like we are missing a tag. > > Also, any idea what it will take to get dbus services to work on ivi images?
Just a note: Since there is no LSM support in kdbus (yet) an IVI system may run, but it's going to have whopping holes in the security policy. Don't get too comfortable with the behavior you get from kdbus, as it will change once the LSM and Smack policy enforcement is implemented. > Thanks, > Kevron > > > > On Fri, Jan 24, 2014 at 12:18 PM, Clark, Joel <[email protected]> wrote: > > > > > > On 01/24/2014 Karol Lewandowski wrote: > >>On 01/24/2014 12:02 PM, Dominig ar Foll (Intel OTC) wrote: > >>> > >>> Le 22/01/14 20:38, Karol Lewandowski a écrit : > >>> To be a viable solution, kdbus will need to land in kernel official > >>> release in a workable model (inclusing smack support). > >> > >>Is it really the case? In tizen we are carrying quite a few patches that > weren't integrated into upstream projects. Our whole security model > depends on this (upstream dbus-daemon doesn't >support smack if I'm not > mistaken). > > > > It is certainly true for Tizen IVI for IA. We usually have 0 out of tree > > kernel > patches. Maintaining out of tree kernel patches is too resource intensive. > > > > Regards > > Joel Clark > > > > _______________________________________________ > > Dev mailing list > > [email protected] > > https://lists.tizen.org/listinfo/dev > _______________________________________________ > Dev mailing list > [email protected] > https://lists.tizen.org/listinfo/dev _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
