Ahh OK. I dont have the code handy, finding them should be a matter of using git format patch between the seandroid and android 4.4.x branches as described on the bitbucket wiki for the project. Then taking what you need and any deps.
Another approach is checking out master and using git blame on the instald/PMS code. On Apr 6, 2015 10:55 AM, "Tai Nguyen (tainguye)" <[email protected]> wrote: > Exactly – I need to find the change to back port it to our code base. > > Tai > > From: William Roberts <[email protected]> > Date: Monday, April 6, 2015 at 10:11 AM > To: Tai Nguyen <[email protected]> > Cc: "[email protected]" <[email protected]>, > Stephen Smalley <[email protected]> > Subject: Re: Question on seapp_context > > The problem is the relabel, you need to back port support for it. > On Apr 6, 2015 10:00 AM, "Tai Nguyen (tainguye)" <[email protected]> > wrote: > >> That is a good question. Currently, we have a constraint requirement that >> a configuration app can write data to this system app directory and we >> don¹t want to give write permission to system_app_data_file to the >> configuration app. Thus, we decide to relabel the dir to app_data_file >> instead. >> >> Tai >> >> On 4/6/15, 8:45 AM, "Stephen Smalley" <[email protected]> wrote: >> >> >Perhaps the first question though that ought to be asked is why wouldn't >> >you want its data to be protected against direct open by untrusted apps? >> > >> >> >> _______________________________________________ >> Seandroid-list mailing list >> [email protected] >> To unsubscribe, send email to [email protected]. >> To get help, send an email containing "help" to >> [email protected]. >> >
_______________________________________________ Seandroid-list mailing list [email protected] To unsubscribe, send email to [email protected]. To get help, send an email containing "help" to [email protected].
