Messages in this thread | | | Date | Sun, 31 May 1998 23:05:20 +0200 | From | Olivier Galibert <> | Subject | Re: [IDEA] Developers: your opinion badly needed ! (Was: [PATCH] /proc/config.gz) |
| |
On Sun, May 31, 1998 at 08:55:01PM +0200, Riccardo Facchetti wrote: > Yes. I know. This is the bigger point against my idea. How to associate in > a secure way a running kernel with its image file, and in any kind of boot > setup. Having an answer to this question will resolve the bloating > problem.
Depends. If you want to be sure to have access to .config/System.map/whatever even if at boot time it was sent to you in morse code through supernovaes explosions, you can't do anything but keeping the data in memory.
If you only want to confirm that the kernel image (to which has been appended all the information you want) you see lying there on the disk in the booted one, simply add a MD5 checksum[1] in the file loaded (not computed) at boot time and accessible through a system call or /proc.
OG.
[1] write a special zone in the file with 16 zeroes, compute the hash, write the result in the zone.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu
| |