From: Andrew Morton <akpm@linux-foundation.org>
To: Arvid Brodin <Arvid.Brodin@xdin.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>,
Cyrill Gorcunov <gorcunov@openvz.org>,
"David Rientjes" <rientjes@google.com>,
"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: [PATCH] fs/proc: Add process text segment md5-summing
Date: Mon, 12 Nov 2012 15:03:25 -0800 [thread overview]
Message-ID: <20121112150325.2516a0bf.akpm@linux-foundation.org> (raw)
In-Reply-To: <50A16BD0.7030600@xdin.com>
On Mon, 12 Nov 2012 21:36:17 +0000
Arvid Brodin <Arvid.Brodin@xdin.com> wrote:
> Adds /proc/<pid>/text_md5sum which, when read, calculates an md5sum over
> the process' text segment. This can detect some cases where the system RAM
> has been disturbed by e.g. ESD or cosmic radiation (on systems where ECC
> is not available). It might also detect some accidental or malicious
> modifications of executables, where the perpetrator has not bothered to
> cover up the tracks.
I thought the review comments regarding the earlier patch were rather
fatal, sorry.
> + Read /proc/<pid>/text_md5sum to get the kernel to perform an MD5
> + checksum over the process' text segment and print the result. This
> + can detect some cases where the system RAM has been disturbed by
> + e.g. ESD or cosmic radiation (on systems where ECC is not available).
> + It might also detect some accidental or malicious modifications of
> + executables, where the perpetrator has not bothered to cover up the
> + tracks.
And that doesn't seem to help much, really. .text is only a small part
of a process's VM and corruption of data, bss, heap or stack is just as
bad.
next prev parent reply other threads:[~2012-11-12 23:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-12 21:36 [PATCH] fs/proc: Add process text segment md5-summing Arvid Brodin
2012-11-12 23:03 ` Andrew Morton [this message]
2012-11-13 2:16 ` Eric W. Biederman
2012-11-14 1:45 ` Arvid Brodin
2012-11-14 0:11 ` Arvid Brodin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20121112150325.2516a0bf.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Arvid.Brodin@xdin.com \
--cc=ebiederm@xmission.com \
--cc=gorcunov@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rientjes@google.com \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.