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  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:	Thu, 29 Oct 2009 12:18:01 -0700 (PDT)
From:	Roland McGrath <>
To:	Ingo Molnar <>
Cc:	Masami Hiramatsu <>,
	Arnaldo Carvalho de Melo <>,
	Frédéric Weisbecker <>,
	lkml <>,
	Steven Rostedt <>,
	Jim Keniston <>,
	Ananth N Mavinakayanahalli <>,
	Christoph Hellwig <>,
	"Frank Ch. Eigler" <>,
	"H. Peter Anvin" <>, Jason Baron <>,
	"K.Prasad" <>,
	Peter Zijlstra <>,
	Srikar Dronamraju <>,
	systemtap <>,
	DLE <>
Subject: Re: [PATCH -tip perf/probes 00/10] x86 insn decoder bugfixes

> Thirdly, i think we should expose the build-id of the kernel and the 
> path to the vmlinux (and modules) via /proc/build-id or so. That way 
> tooling can find the vmlinux file and can validate that it matches the 
> kernel's signature. (maybe include a file date as well - that's a faster 
> check than a full build-id checksum, especially for large kernels)

You seem to be confused about what build IDs are.  There is no "checksum
validation".  Once the bits are stored there is no calculation ever done
again, only exact comparison with an expected build ID bitstring.  The size
of an object file is immaterial.

As Frank mentioned, the kernel's and modules' allocated ELF notes (and thus
build IDs) are already exposed in /sys.  Tools like "eu-unstrip -nk" use
this information today.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists