[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Sat, 31 Dec 2022 18:27:58 +0100
From: Solar Designer <solar@...nwall.com>
To: David Laight <David.Laight@...LAB.COM>
Cc: 'Shawn Webb' <shawn.webb@...denedbsd.org>,
"oss-security@...ts.openwall.com" <oss-security@...ts.openwall.com>,
Alejandro Colomar <alx.manpages@...il.com>,
Michael Kerrisk <mtk.manpages@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-man@...r.kernel.org" <linux-man@...r.kernel.org>
Subject: Re: [patch] proc.5: tell how to parse /proc/*/stat correctly
Hi all,
Let's wind this oss-security thread down as it relates to brainstorming
and commenting on totally new designs - no more of that, please.
Many things were said, but realistically the interface isn't _that_
broken (this can be parsed correctly, and procps-ng manages to) and is
(hopefully) not going to change much (in my opinion, and I know I'm not
alone in this, most of the proposals would make things worse overall).
Somewhat realistically, one possible change is replacing the most risky
characters, such as braces and anything <= ASCII 32, perhaps with '?'
to match what procps-ng is doing. Perhaps do this either on all updates
of "comm" or in all places where "comm" is reported to userspace
(including procfs and kernel messages, by calling a common function).
"comm" isn't the full process name anyway - it's often truncated - so it
can reasonably be made safer in other ways as well. As an option, the
replacing of whitespace (ASCII 32) and braces could be limited to the
"stat" file, but the control characters are (even more) problematic with
other interfaces where "comm" is exposed, so replacing them should
probably be global.
Happy New Year!
Alexander
Powered by blists - more mailing lists
Please check out the
Open Source Software Security Wiki, which is counterpart to this
mailing list.
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
