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: <CAGXu5jKbvXdtOQMVV3Jig-cCd=yfMYTF5gZSReAxkEEfs198ow@mail.gmail.com>
Date:	Fri, 14 Mar 2014 13:15:02 -0700
From:	Kees Cook <keescook@...omium.org>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Dave Jones <davej@...hat.com>,
	Sasha Levin <sasha.levin@...cle.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [RFC] improve_stack: make stack dump output useful again

On Fri, Mar 14, 2014 at 12:41 PM, Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
> On Fri, Mar 14, 2014 at 12:32 PM, Linus Torvalds
> <torvalds@...ux-foundation.org> wrote:
>>
>> Hmm. Do you have CONFIG_KALLSYMS enabled?
>
> Just to clarify. KALLSYMS is required to figure out the symbol
> addresses on a kaslr system. There's no way to look them up in a
> System.map file or the object file, since the addresses aren't going
> to match.
>
> Your symptoms really sound like you might not have KALLSYMS enabled.
>
> I wonder if we have a "select KALLSYMS" as part of RANDOMIZE_BASE,
> since you need it for debug messages too (random hex numbers aren't
> too useful ;)

My weak preference would be to allow to build without that hard
requirement (citing imagined space savings, blah blah). But since
everything I normally use has KALLSYMS, I wouldn't object to doing it
either. :)

-Kees

-- 
Kees Cook
Chrome OS Security
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ