Hello, This might be an easy question but I can't seem to find a clear answer anywhere. Apologies if this isn't the right mailing list to ask these kind of things and thank you for your time. :) ----------------------------------- The scenario is as follows:
I have a third party app (aka not a system app so just installed by a user/marketplace service) called MyApp. Inside MyApp I have some jni bindings that call native C code. This native C code starts two processes (let's call them ProcessA and ProcessB). From that point on the jni bindings communicate with ProcessA only. ProcessB in the meantime forks and now has 1-3 children processes. ProcessB acts like a manager for those processes and is their parent. The IPC in both cases (between processA <-processB and between processB <-> children) is done via Unix Sockets. This works fine with glibc and on *nix OSes without SELinux. My question is: would the default SELinux policy used in most devices cause problems with the usage of unix sockets for IPC? I know that using the native binders provided by bionic is preffered for IPC but it would be pretty costly to reimplement it again in my app. If it's not feasible by default what kind of changes would be necessary to make it work? Kind regards, Paul _______________________________________________ Seandroid-list mailing list [email protected] To unsubscribe, send email to [email protected]. To get help, send an email containing "help" to [email protected].
