From: Solar Designer <solar@openwall.com>
To: kernel-hardening@lists.openwall.com
Cc: Pavel Labushev <p.labushev@gmail.com>
Subject: [kernel-hardening] /proc/PID directory hiding (was: [owl-dev] segoon's status report - #1 of 15)
Date: Sat, 4 Jun 2011 22:19:11 +0400 [thread overview]
Message-ID: <20110604181911.GC5034@openwall.com> (raw)
In-Reply-To: <4DE139FE.8050808@gmail.com>
Pavel, Vasiliy -
On Sun, May 29, 2011 at 02:07:58AM +0800, Pavel Labushev wrote:
> 24.05.2011 23:12, Vasiliy Kulikov wrote:
>
> > I've implemented restricted perms, but didn't do actual hiding
> > directories. In grsecurity it is implemented by hiding directories from
> > processes that cannot access them.
> >
> > I think it may be defective by design because there are many other ways
>
> It is:
> $ python -c 'import os; print os.stat("/proc/1")'
> posix.stat_result(st_mode=16744, st_ino=535821L, st_dev=3L, st_nlink=6,
> st_uid=0, st_gid=0, st_size=0L, st_atime=1306605485, st_mtime=1306605485,
> st_ctime=1306605485)
>
> It's a known flaw and AFAIR it was considered irrelevant.
Is the above on grsecurity?
I think we may choose to restrict more than just directory listing -
that is, have these entries invisible even when referenced by full
pathnames.
As to probing for PIDs with syscalls such as kill(2), we may deal with
that as well (but we'd need to consider potential performance impact, as
well as timing attacks), or may choose not to do it. Arguably, we
primarily want to hide UIDs/GIDs of running processes, not their PIDs.
Alexander
next parent reply other threads:[~2011-06-04 18:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110518150601.GA2921@albatros>
[not found] ` <20110524023409.GC12486@openwall.com>
[not found] ` <20110524151246.GA3401@albatros>
[not found] ` <4DE139FE.8050808@gmail.com>
2011-06-04 18:19 ` Solar Designer [this message]
2011-06-04 20:20 ` [kernel-hardening] /proc/PID directory hiding (was: [owl-dev] segoon's status report - #1 of 15) Vasiliy Kulikov
2011-06-04 21:03 ` Solar Designer
2011-06-05 0:10 ` [kernel-hardening] /proc/PID directory hiding Pavel Labushev
2011-06-05 1:18 ` Pavel Labushev
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=20110604181911.GC5034@openwall.com \
--to=solar@openwall.com \
--cc=kernel-hardening@lists.openwall.com \
--cc=p.labushev@gmail.com \
/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