Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 1 Nov 2018 01:21:00 +0200
From: Ahmed Soliman <>
To: Igor Stoppa <>
Cc: Paolo Bonzini <>, Radim Krčmář <>, 
	nathan Corbet <>, Thomas Gleixner <>, Ingo Molnar <>, 
	Borislav Petkov <>, "H. Peter Anvin" <>, "the arch/x86 maintainers" <>,,,, 
	김인겸 <>, 
	Kernel Hardening <>,, 
	Boris Lukashev <>, Hossam Hassan <>, 
	Ahmed Lotfy <>, Mohamed Azab <>
Subject: Re: [PATCH V5 0/5] KVM: X86: Introducing ROE Protection Kernel Hardening

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:
> In my case the protection would extend also to write-rate type of data.
> There is an open problem of identifying legitimate write-rare
> operations, however it should be possible to provide at least a certain
> degree of confidence.

I have checked your patch set. In our work we were originally planning to do
something similar to write_rare just so we can differentiate between memory
chunks that may be modified and those that will be set once and never modify.
I see you are planning to do a white paper too, actually we are doing
an academic
paper based on our work. If you would like to collaborate, so that ROE
and write_rare
would integrate well from the beginning, we will be glad to do so.

Junior Researcher , IoT and Cyber Security lab, SmartCI , Alexandria
University, & CIS @  VMI

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.