Jonathan Cameron wrote:
> I'm on a train so can't check the original thread right now (and will probably
> forget to do so later!). I am guessing the new functions are introduced
> earlier in the series?
Yeah, patch 1 is a prerequisite for all the subsequent patches.
> Hence
Jonathan Cameron wrote:
> I'm on a train so can't check the original thread right now (and will probably
> forget to do so later!). I am guessing the new functions are introduced
> earlier in the series?
Yeah, patch 1 is a prerequisite for all the subsequent patches.
> Hence for now I'll
On 01/12/16 13:50, William Breathitt Gray wrote:
> On Thu, Dec 01, 2016 at 12:30:55PM +, David Howells wrote:
>> When the kernel is running in secure boot mode, we lock down the kernel to
>> prevent userspace from modifying the running kernel image. Whilst this
>> includes prohibiting access
On 01/12/16 13:50, William Breathitt Gray wrote:
> On Thu, Dec 01, 2016 at 12:30:55PM +, David Howells wrote:
>> When the kernel is running in secure boot mode, we lock down the kernel to
>> prevent userspace from modifying the running kernel image. Whilst this
>> includes prohibiting access
On Thu, Dec 01, 2016 at 12:30:55PM +, David Howells wrote:
>When the kernel is running in secure boot mode, we lock down the kernel to
>prevent userspace from modifying the running kernel image. Whilst this
>includes prohibiting access to things like /dev/mem, it must also prevent
>access by
On Thu, Dec 01, 2016 at 12:30:55PM +, David Howells wrote:
>When the kernel is running in secure boot mode, we lock down the kernel to
>prevent userspace from modifying the running kernel image. Whilst this
>includes prohibiting access to things like /dev/mem, it must also prevent
>access by
When the kernel is running in secure boot mode, we lock down the kernel to
prevent userspace from modifying the running kernel image. Whilst this
includes prohibiting access to things like /dev/mem, it must also prevent
access by means of configuring driver modules in such a way as to cause a
When the kernel is running in secure boot mode, we lock down the kernel to
prevent userspace from modifying the running kernel image. Whilst this
includes prohibiting access to things like /dev/mem, it must also prevent
access by means of configuring driver modules in such a way as to cause a
8 matches
Mail list logo