Re: [PATCH] Vtable pointer verification (corruption/attach detection -- new feature

2013-03-26 Thread Florian Weimer
On 02/01/2013 12:42 AM, Caroline Tice wrote: If this data could be emitted in a declarative fashion, it might be possible to emit it by default, in a separate ELF section. This way, it is always there when needed, and it wouldn't have any performance impact if not used. That might be possible;

Re: [PATCH] Vtable pointer verification (corruption/attach detection -- new feature

2013-01-31 Thread Caroline Tice
cmt...@google.com On Wed, Jan 30, 2013 at 2:09 AM, Florian Weimer wrote: > On 11/01/2012 09:07 PM, Caroline Tice wrote: >> >> We have been developing a new security hardening feature for GCC that >> is designed to detect and handle (during program execution) when a >> vtable pointer that is abou

Re: [PATCH] Vtable pointer verification (corruption/attach detection -- new feature

2013-01-30 Thread Florian Weimer
On 11/01/2012 09:07 PM, Caroline Tice wrote: We have been developing a new security hardening feature for GCC that is designed to detect and handle (during program execution) when a vtable pointer that is about to be used for a virtual function call is not a valid vtable pointer for that call (i.

Re: [PATCH] Vtable pointer verification (corruption/attach detection -- new feature

2012-11-04 Thread Xinliang David Li
Can you split the patch into two parts? One for runtime and and one for GCC ? Please also use -up option in the diff command to generate the patch file. thanks, David On Thu, Nov 1, 2012 at 1:07 PM, Caroline Tice wrote: > We have been developing a new security hardening feature for GCC that > i