linux-kernel - Re: Extending coredump note section to contain filenames

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] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 13 Mar 2012 01:46:42 +0100
From:	Jan Kratochvil <jan.kratochvil@...hat.com>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Denys Vlasenko <dvlasenk@...hat.com>,
	Roland McGrath <roland@...k.frob.com>,
	linux-kernel@...r.kernel.org, Oleg Nesterov <oleg@...hat.com>,
	Kushal Das <kdas@...hat.com>
Subject: Re: Extending coredump note section to contain filenames

On Tue, 13 Mar 2012 01:42:18 +0100, H. Peter Anvin wrote:
> There is no 100% reliable solution possible -- you have no guarantee of
> any kind that the library executable still exists.

I have guarantee that the library binary mapped in memory identified by
build-id can be found out there in the could.  There is no other guarantee.
And this guarantee fails with other solutions.

If you say that it is _additional_ info to build-id then yes, one can always
use build-id if everything else fails.  But then the non-build-id information
is redundant and it can just lead to wrong toolchain solutions - which has
already happened (Apport).

Regards,
Jan
--
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/