Hi,
Alberto Mardegan (2020-04-02):
> On 02/04/20 16:48, intrigeri wrote:
>> At Tails we do ship a binary, compiled policy in our live system:
>>
>>
>> https://salsa.debian.org/tails-team/tails/-/blob/master/config/chroot_local-hooks/99-cache-AppArmor-policy
>>
>> https://salsa.debian.org/ta
On 4/2/20 7:53 AM, Alberto Mardegan wrote:
> Hi,
>
> On 02/04/20 16:48, intrigeri wrote:
>> At Tails we do ship a binary, compiled policy in our live system:
>>
>>
>> https://salsa.debian.org/tails-team/tails/-/blob/master/config/chroot_local-hooks/99-cache-AppArmor-policy
>>
>> https://sals
On 4/2/20 6:48 AM, intrigeri wrote:
> Hi,
>
> Alberto Mardegan (2020-04-02):
>> My first question is whether this is actually doable: is the binary
>> format of a cached profile independent from the machine architecture in
>> which it is generated?
>
> I don't know about architecture portability.
Hi,
On 02/04/20 16:48, intrigeri wrote:
> At Tails we do ship a binary, compiled policy in our live system:
>
>
> https://salsa.debian.org/tails-team/tails/-/blob/master/config/chroot_local-hooks/99-cache-AppArmor-policy
>
> https://salsa.debian.org/tails-team/tails/-/blob/master/config/chr
Hi,
Alberto Mardegan (2020-04-02):
> My first question is whether this is actually doable: is the binary
> format of a cached profile independent from the machine architecture in
> which it is generated?
I don't know about architecture portability.
At Tails we do ship a binary, compiled policy i
Hi all!
I'm trying to speed up the first device boot by generating a cache of
the profiles. The target machine is running a Yocto image, so it would
feel natural if the profile cache is also generated by Yocto.
My first question is whether this is actually doable: is the binary
format of a cache
