From: Vasiliy Kulikov <segoon@openwall.com>
To: kernel-hardening@lists.openwall.com
Subject: [kernel-hardening] proc info restrictions problem
Date: Sat, 18 Jun 2011 14:42:07 +0400 [thread overview]
Message-ID: <20110618104207.GA13752@albatros> (raw)
Hi,
I'm trying to adapt HARDEN_PROC restrictions to taskstats and proc
connector and stuck with a problem. proc connector is a special
broadcast netlink socket that gathers all proc information (fork, exit,
exec). There is one mechanism to filter the data coming into actual
receiving sockets:
int netlink_broadcast_filtered(..., void (*filter)(sock, skb, data), data)
"sock" is receiving socket, filter answers whether the skb should be
send to "sock".
The thing is a socket has no actual information about what specific task
owns it as it might be owned by multiple tasks simultaneously. So, I
cannot check for PTRACE_MODE_READ as I have only "struct cred*", not
"struct task_struct*". Some LSMs use only cred part of task, but SMACK
already uses some information from task_struct, so changing ptrace and LSM
interface is impossible.
Manual check for {e,r,fs,s}{u,g}id and capabilities via
cap_ptrace_access_check() might not be sufficient because of possible
additional LSM restrictions and policies.
I feel doubt whether ptrace_may_access() may be changed to something
more simple. Both -ow and -grsecurity use changed posix permissions and
gid on procfs files, so maybe just match subject's euid vs. object's uid?
Thanks,
--
Vasiliy
next reply other threads:[~2011-06-18 10:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-18 10:42 Vasiliy Kulikov [this message]
2011-06-18 18:28 ` [kernel-hardening] Re: proc info restrictions problem Vasiliy Kulikov
2011-06-19 14:18 ` Vasiliy Kulikov
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=20110618104207.GA13752@albatros \
--to=segoon@openwall.com \
--cc=kernel-hardening@lists.openwall.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