On Fri, Sep 16, 2016 at 8:06 PM, Stephen Smalley <s...@tycho.nsa.gov> wrote:
> On 09/16/2016 02:57 PM, Janis Danisevskis wrote:
> > I have started implementing an arch string patch. Unfortunately, i did
> > not manage to finish it before I had to leave the office today.
> > In essence I did this:
> > The regex_arch_string has three components: the pointer width determined
> > by sizeof(void*), PCRE2_SIZE width determined by sizeof(), and
> > endianess determined by
> > __BYTE_ORDER__==__ORDER_BIG/LITTEL_ENDIAN__
> > For example, the resulting string for x86_64 and aarch64el should look
> > this: "8-8-el".
> > I bumped the compiled context version number and added the string
> > right after the version in the output.
> > Comments?
> What's the error handling when the versions do not match? Just ignore
> the compiled regexes in file_contexts.bin?
> Yes, If the version and arch match attempt to load the compiled regexes
from the file. Otherwise, skip the corresponding regions of the file and
leave the regex field NULL, so that they will be compiled on first use.
Seandroid-list mailing list
To unsubscribe, send email to seandroid-list-le...@tycho.nsa.gov.
To get help, send an email containing "help" to