On Wed, May 13, 2020 at 10:48:04AM -0400, Daniele Buono wrote:
> Hello everybody, just pinging since it it's been a few days.
Hi Daniele,
Sorry I'm late to the party. This looks useful, the patches are not
invasive and provide the option of enabling extra security.
I have left comments on
Hello everybody, just pinging since it it's been a few days.
On 5/5/2020 9:56 AM, Philippe Mathieu-Daudé wrote:
On 5/5/20 3:31 PM, Daniel P. Berrangé wrote:
On Tue, May 05, 2020 at 03:15:18PM +0200, Philippe Mathieu-Daudé wrote:
+Alex & Daniel who keep track on CI stuff.
On 4/29/20 9:44 PM,
On 5/5/20 3:31 PM, Daniel P. Berrangé wrote:
On Tue, May 05, 2020 at 03:15:18PM +0200, Philippe Mathieu-Daudé wrote:
+Alex & Daniel who keep track on CI stuff.
On 4/29/20 9:44 PM, Daniele Buono wrote:
LLVM supports SafeStack instrumentation to protect against stack buffer
overflows, since
On Tue, May 05, 2020 at 03:15:18PM +0200, Philippe Mathieu-Daudé wrote:
> +Alex & Daniel who keep track on CI stuff.
>
> On 4/29/20 9:44 PM, Daniele Buono wrote:
> > LLVM supports SafeStack instrumentation to protect against stack buffer
> > overflows, since version 3.7
> >
> > From
+Alex & Daniel who keep track on CI stuff.
On 4/29/20 9:44 PM, Daniele Buono wrote:
LLVM supports SafeStack instrumentation to protect against stack buffer
overflows, since version 3.7
From https://clang.llvm.org/docs/SafeStack.html:
"It works by separating the program stack into two distinct
On 4/29/20 9:44 PM, Daniele Buono wrote:
LLVM supports SafeStack instrumentation to protect against stack buffer
overflows, since version 3.7
From https://clang.llvm.org/docs/SafeStack.html:
"It works by separating the program stack into two distinct regions: the
safe stack and the unsafe
LLVM supports SafeStack instrumentation to protect against stack buffer
overflows, since version 3.7
>From https://clang.llvm.org/docs/SafeStack.html:
"It works by separating the program stack into two distinct regions: the
safe stack and the unsafe stack. The safe stack stores return addresses,
