Re: [kernel-hardening] [PATCH] use get_random_long for the per-task stack canary

2017-05-04 Thread Kees Cook
On Thu, May 4, 2017 at 7:04 AM, Rik van Riel wrote: > On Thu, 2017-05-04 at 09:32 -0400, Daniel Micay wrote: >> The stack canary is an unsigned long and should be fully initialized >> to >> random data rather than only 32 bits of random data. >> >> Cc: sta...@vger.kernel.org >> Signed-off-by: Dani

Re: [kernel-hardening] [PATCH] use get_random_long for the per-task stack canary

2017-05-04 Thread Rik van Riel
On Thu, 2017-05-04 at 09:32 -0400, Daniel Micay wrote: > The stack canary is an unsigned long and should be fully initialized > to > random data rather than only 32 bits of random data. > > Cc: sta...@vger.kernel.org > Signed-off-by: Daniel Micay > Acked-by: Rik van Riel

Re: [PATCH] use get_random_long for the per-task stack canary

2017-05-04 Thread Arjan van de Ven
On 5/4/2017 6:32 AM, Daniel Micay wrote: The stack canary is an unsigned long and should be fully initialized to random data rather than only 32 bits of random data. that makes sense to me... ack

[PATCH] use get_random_long for the per-task stack canary

2017-05-04 Thread Daniel Micay
The stack canary is an unsigned long and should be fully initialized to random data rather than only 32 bits of random data. Cc: sta...@vger.kernel.org Signed-off-by: Daniel Micay --- kernel/fork.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/fork.c b/kernel/fork.c