Hello Ahmed,
On 01/11/2018 01:21, Ahmed Soliman wrote:
Hello Igor,
This is very interesting, because it seems a very good match to the work
I'm doing, for supporting the creation of more targets for protection:
https://www.openwall.com/lists/kernel-hardening/2018/10/23/3
In my case the protec
Hello Igor,
> This is very interesting, because it seems a very good match to the work
> I'm doing, for supporting the creation of more targets for protection:
>
> https://www.openwall.com/lists/kernel-hardening/2018/10/23/3
>
> In my case the protection would extend also to write-rate type of data
On 10/26/2018 05:12 PM, Ahmed Abd El Mawgood wrote:
> This is the 5th version which is 4th version with minor fixes. ROE is a
> hypercall that enables host operating system to restrict guest's access to its
> own memory. This will provide a hardening mechanism that can be used to stop
> rootkits
On Mon, 29 Oct 2018 at 08:46, Ingo Molnar wrote:
>
>
> * Ahmed Abd El Mawgood wrote:
>
> > This is the 5th version which is 4th version with minor fixes. ROE is a
> > hypercall that enables host operating system to restrict guest's access to
> > its
> > own memory. This will provide a hardening
Hi,
On 26/10/2018 16:12, Ahmed Abd El Mawgood wrote:
This is the 5th version which is 4th version with minor fixes. ROE is a
hypercall that enables host operating system to restrict guest's access to its
own memory. This will provide a hardening mechanism that can be used to stop
rootkits from
* Ahmed Abd El Mawgood wrote:
> This is the 5th version which is 4th version with minor fixes. ROE is a
> hypercall that enables host operating system to restrict guest's access to its
> own memory. This will provide a hardening mechanism that can be used to stop
> rootkits from manipulating k
