public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Joakim Tjernlund <joakim.tjernlund@transmode.se>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: ls -l /proc/1/exe -> Permission denied
Date: Sun, 20 Jul 2014 14:08:35 +0200	[thread overview]
Message-ID: <53CBB143.1020206@nod.at> (raw)
In-Reply-To: <87bnskxn7g.fsf@igel.home>

Am 20.07.2014 13:51, schrieb Andreas Schwab:
> Richard Weinberger <richard.weinberger@gmail.com> writes:
>> Do you have an example?
> 
> proc symlinks are special because they actually resolve to the inode.

Ah. If an attacker manages the kernel to follow the symlink he could
indirectly access that file.
Thanks for pointing this out!

Thanks,
//richard

  parent reply	other threads:[~2014-07-20 12:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-17 11:18 ls -l /proc/1/exe -> Permission denied Joakim Tjernlund
2014-07-18 12:58 ` Richard Weinberger
2014-07-18 13:49   ` Joakim Tjernlund
     [not found]   ` <OF542E7A59.842197B0-ONC1257D19.004B7FF4-C1257D19.004BEC7C@LocalDomain>
2014-07-18 15:05     ` Joakim Tjernlund
2014-07-19 20:06       ` Richard Weinberger
2014-07-19 20:21 ` Andreas Schwab
2014-07-20  9:02   ` Joakim Tjernlund
2014-07-20 10:55     ` Andreas Schwab
2014-07-20 11:06       ` Richard Weinberger
2014-07-20 11:19         ` Joakim Tjernlund
2014-07-20 11:51         ` Andreas Schwab
2014-07-20 12:05           ` Richard Weinberger
2014-07-20 12:05           ` Richard Weinberger
2014-07-20 19:15             ` Joakim Tjernlund
2014-07-20 20:00               ` Richard Weinberger
2014-07-20 22:05                 ` Joakim Tjernlund
2014-07-20 12:08           ` Richard Weinberger [this message]
2014-07-21 17:48             ` Eric W. Biederman

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=53CBB143.1020206@nod.at \
    --to=richard@nod.at \
    --cc=joakim.tjernlund@transmode.se \
    --cc=linux-kernel@vger.kernel.org \
    --cc=schwab@linux-m68k.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox