| 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
| ||
|
Message-Id: <1175453887.14923.73.camel@laptopd505.fenrus.org> Date: Sun, 01 Apr 2007 11:58:07 -0700 From: Arjan van de Ven <arjan@...radead.org> To: Edgardo Hames <ehames@...il.com> Cc: linux-kernel@...r.kernel.org Subject: Re: Rebuilding and checksumming the Linux kernel On Sun, 2007-04-01 at 15:56 -0300, Edgardo Hames wrote: > I'm working on a project with teams spread across the world and we all > work on the same repository patching the kernel and then integrating > into a common main branch. Even though we label the source code, we > would like to make sure that we are all building the same kernel by > running md5sum on the resulting binary. > > Right now, this is not possible because the kernel includes a > timestamp and a build number on the binary. What are this timestamps > used for? Can we just remove them? Is there any other thing that may > lead to different binaries? (we are using the exact toolchains and > build machines, so we can assume that the same executable is generated > if the input source is the same). elfutils has a "elfcmp" program that may be useful for you another trick could be to run objdump -d on the vmlinux, and then compare the assembly file.. you could even grep out any known date like things that way,, - 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