On Wed, 11 Jul 2007, Roland McGrath wrote:
>
> It will give them at least as reliable an identification of the kernel
> binary as the "uname -rv" info if they have access to a set of candidate
> known binaries to select from.
Ok, that doesn't sound bad. Is the "note" something global for the whole
thing, or are there per-object file notes that you can parse (ie can you
figure out which modules are linked in some way?)
If it's basically just a set of hashes, I won't worry.
> I have no special opinions about that, but I haven't seen an install where
> the /boot files were not readable anyway. But certainly in a chroot or
> such, you won't have /boot at all but might have /proc and /sys.
Yah. Not that we generally do perfectly here, but that's the kind of thing
I'd prefer.
> All in all, this seems like a question of local policy.
Is there any reason for it to be readable by anybody but the sysadmin?
It's not like you're likely to do things like kernel debugging without
root privileges?
So if the *common* thing is that normally people have root who really
care, and the distro could (if it wants to) just chmod the /sysfs file
appropriately, maybe that would allow the best of both worlds? Just
default to it being root-readable, but let the distro override it at
boot-time?
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
