Date: Thu, 24 Jul 2014 08:51:47 +0100 From: "Robert N. M. Watson" <rwatson@FreeBSD.org> To: Pedro Giffuni <pfg@freebsd.org> Cc: PaX Team <pageexec@freemail.hu>, "freebsd-arch@freebsd.org" <freebsd-arch@freebsd.org>, Oliver Pinter <oliver.pntr@gmail.com>, Bryan Drewery <bdrewery@FreeBSD.org>, Shawn Webb <lattera@gmail.com> Subject: Re: [RFC] ASLR Whitepaper and Candidate Final Patch Message-ID: <860889F3-EA75-4C08-A1A4-904CE7A94899@FreeBSD.org> In-Reply-To: <D4BC6F5C-E041-42BA-B798-85F7911390A6@freebsd.org> References: <96C72773-3239-427E-A90B-D05FF0F5B782@freebsd.org> <20140720201858.GB29618@pwnie.vrt.sourcefire.com> <alpine.BSF.2.11.1407230017490.88645@fledge.watson.org> <20140723004543.GH29618@pwnie.vrt.sourcefire.com> <D7CEDB47-2818-461A-BB70-479BEBDCEEE9@freebsd.org> <20140723234455.GP29618@pwnie.vrt.sourcefire.com> <D4BC6F5C-E041-42BA-B798-85F7911390A6@freebsd.org>
index | next in thread | previous in thread | raw e-mail
>>>>> Great news that this work is coming to fruition -- ASLR is long overdue. >>>>> >>>>> Are you having any luck with performance measurements? Unixbench seems like a >>>>> good starting point, but I wonder if it would be useful to look, in >>>>> particular, at memory-mapping intensive workloads that might be affected as a >>>>> result of changes in kernel VM data-structure use, or greater fragmentation of >>>>> the address space. I'm not sure I have a specific application here in mind -- >>>>> in the past I might have pointed out tools such as ElectricFence that tend to >>>>> increase fragmentation themselves. >>>> >>>> The unixbench tests on that laptop have finished. However, I've been >>>> fighting a pesky migraine these last couple days, so I haven't had the >>>> opportunity to aggregate the results into a nice little spreadsheet. I'm >>>> hoping to finish it up by the end of the week. >>>> >>>> I'll take a look at ElectricFence this weekend. Additionally, I have a >>>> netbook somewhere. Once I find it and its power cord, I'll install >>>> FreeBSD/x86 and re-run the same tests on that. >>> >>> Somewhat related to ElectricFence? will ASLR have an adverse effect on debuggers? >>> >>> I googled around and got to this: >>> >>> http://www.outflux.net/blog/archives/2010/07/03/gdb-turns-off-aslr/ >> >> I've been doing all my ClamAV development on my FreeBSD box with ASLR >> enabled. Development tools like gdb and valgrind work great, even with >> corefiles. I have not, however, tried lldb. > > OK, but it’s worth to take a look if we need to support something to turn it off. > Apparently gdb disables ASLR on MacOSX too: > > http://reverse.put.as/2011/08/11/how-gdb-disables-aslr-in-mac-os-x-lion/ > > Pedro. >home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?860889F3-EA75-4C08-A1A4-904CE7A94899>