linux-kernel - Re: When was ASLR introduced in the Linux kernel?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <1291140619.2904.144.camel@edumazet-laptop>
Date:	Tue, 30 Nov 2010 19:10:19 +0100
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	Victor van der Veen <vvdveen@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: When was ASLR introduced in the Linux kernel?

Le mardi 30 novembre 2010 à 18:50 +0100, Victor van der Veen a écrit :

> Thanks, but this was not what I was really looking for. However,
> searching for 'randomize_va_space' led me to a thread on lkml started by
> Arjan van de Ven on January 27th, 2005:
> http://lkml.org/lkml/2005/1/27/56
> 
> It would be great if someone can provide more details on this subject:
>   1) when was randomize_va_space introduced? (probably somewhere in
> 2.6.11.x)

	who cares ?

>   2) when was it enabled by default (2.6.12.? but no announcement in
> changelog?)

commit 42a172a814759a29020e5d1ee580bf4eb86afed2
Author: arjan <arjan>
Date:   Sat Mar 5 17:25:41 2005 +0000

    [PATCH] Randomisation: enable by default
    
    Signed-off-by: Arjan van de Ven <arjan@...radead.org>
    Signed-off-by: Ingo Molnar <mingo@...e.hu>
    Signed-off-by: Andrew Morton <akpm@...l.org>
    Signed-off-by: Linus Torvalds <torvalds@...l.org>
    
    BKrev: 4229eb95j12voWjpsZzY2Wlm6P7Mvg

# git describe --contains 42a172a8
v2.6.11.3~887

>   3) which additions were added in later releases? (and when?)


commit 32a932332c8bad842804842eaf9651ad6268e637
Author: Ingo Molnar <mingo@...e.hu>
Date:   Wed Feb 6 22:39:44 2008 +0100

    brk randomization: introduce CONFIG_COMPAT_BRK
    
    based on similar patch from: Pavel Machek <pavel@....cz>
    
    Introduce CONFIG_COMPAT_BRK. If disabled then the kernel is free
    (but not obliged to) randomize the brk area.
    
    Heap randomization breaks ancient binaries, so we keep COMPAT_BRK
    enabled by default.
    
    Signed-off-by: Ingo Molnar <mingo@...e.hu>

git describe --contains 32a932332c8bad842804842eaf9651ad6268e637
v2.6.25-rc1~513^2~15



--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/