archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <>
To: "Theodore Y. Ts'o" <>
Cc: TongZhang <>, Cyrill Gorcunov <>,,,
Subject: Re: Leaking path for set_task_comm
Date: Wed, 26 Sep 2018 23:39:03 +0100	[thread overview]
Message-ID: <20180926233903.38fb598a@alans-desktop> (raw)
In-Reply-To: <>

> Trying to depend on task name for anything security sensitive is at
> _really_ bad idea, so it seems unlikely that a LSM would want to
> protect the process name.  (And if they did, the first thing I would
> ask is "Why?  What are you trying to do?  Do you realize how many
> *other* ways the process name can be spoofed or otherwise controlled
> by a potentially malicious user?")

Two processes that should not be able to otherwise communicate can keep
changing their name to a chunk of data, waiting for an ack flag name
change back.


      reply	other threads:[~2018-09-28 14:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-25 17:27 Leaking path for set_task_comm Tong Zhang
2018-09-25 18:39 ` Cyrill Gorcunov
2018-09-26  0:44   ` TongZhang
2018-09-26  3:16     ` Theodore Y. Ts'o
2018-09-26 22:39       ` Alan Cox [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180926233903.38fb598a@alans-desktop \ \ \ \ \ \ \ \

* 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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).