[prev in list] [next in list] [prev in thread] [next in thread] 

List:       oss-security
Subject:    [oss-security] Re: [kernel-hardening] Re: Stack guard canary massaging
From:       Daniel Micay <danielmicay () gmail ! com>
Date:       2016-10-31 11:41:04
Message-ID: 1477914064.3558.4.camel () gmail ! com
[Download RAW message or body]


On Mon, 2016-10-31 at 12:22 +0100, Solar Designer wrote:
> On Mon, Oct 31, 2016 at 11:48:45AM +0100, Florian Weimer wrote:
> > Sorry for cross-posting.
> 
> Sorry to bikeshed, but I think this isn't a kernel-hardening topic at
> all, so the thread should continue on oss-security only, please.
> 
> Florian, if there's a reason why you think it's kernel-hardening
> related, please let me know.    To me, it looks like userspace hardening
> that is not even kernel-assisted (at least not directly in this place,
> even though the kernel may have helped provide the random numbers).
> 
> If your cross-posting was to reach more of the right people, then you
> have already done so, and they can join oss-security now. ;-)
> 
> Alexander

The kernel supports SSP but it doesn't appear to do the same thing.

arch/*/include/asm/stackprotector.h

Why do the non-x86 implementations XOR in LINUX_VERSION_CODE though? Is
it supposed to be a placeholder for a random at compile-time value? :\

It's not harmful but that's just... weird.
["signature.asc" (application/pgp-signature)]

[prev in list] [next in list] [prev in thread] [next in thread]