| 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
| ||
|
Date: Tue, 13 Mar 2012 13:19:14 +0100 From: Jan Kratochvil <jan.kratochvil@...hat.com> To: Denys Vlasenko <dvlasenk@...hat.com> Cc: 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 13:12:41 +0100, Denys Vlasenko wrote: > ec1fd70dbee0db36eff9527254d9d2bbfd260f13 0x2093 - /usr/bin/md5sum > ec1fd70dbee0db36eff9527254d9d2bbfd260f13 0x1659 - /usr/bin/md5sum > > If anyone would want to use this tool on a large collection > of coredumps with the intent of fishing out similar crashes In such moment it is already on public Internet and the build-id -> name mapping database is available. Or it rather would be available if the Darkserver would be finished. So far I have only always seen every project for build-id targeted at getting rid of the build-id and map it back to the ambiguous filenames / package names. In such case there could filename / package name already in the ELF header. build-id should be there as a feature, not as a complication. > (this is not a theoretical assumption, we *do* have people > who badly need this feature), they won't get nice names of binaries, If someone does 'cp /usr/bin/md5sum ~/bin/mysum' then you either get unidentifiable names or even misleading names. 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/
Powered by blists - more mailing lists