From: Pablo Neira <pablo@eurodev.net>
To: Chris Wright <chrisw@osdl.org>
Cc: netdev@oss.sgi.com, davem@davemloft.net, jmorris@redhat.com,
sds@epoch.ncsc.mil, serue@us.ibm.com
Subject: Re: [RFC][PATCH 2/3] netlink check sender, audit
Date: Sat, 12 Feb 2005 17:48:11 +0100 [thread overview]
Message-ID: <420E334B.8060805@eurodev.net> (raw)
In-Reply-To: <20050212010504.X24171@build.pdx.osdl.net>
Chris Wright wrote:
>Add audit_check_sender() function for audit netlink messages. This can also
>be used to set the loginuid, although I left that off for the moment.
>
>===== kernel/audit.c 1.9 vs edited =====
>--- 1.9/kernel/audit.c 2005-01-30 22:33:47 -08:00
>+++ edited/kernel/audit.c 2005-02-11 22:25:33 -08:00
>@@ -309,27 +309,36 @@ nlmsg_failure: /* Used by NLMSG_PUT */
> * Check for appropriate CAP_AUDIT_ capabilities on incoming audit
> * control messages.
> */
>-static int audit_netlink_ok(kernel_cap_t eff_cap, u16 msg_type)
>+static int audit_check_sender(struct sk_buff *skb)
> {
>- int err = 0;
>+ struct nlmsghdr *nlh;
>+ u16 msg_type;
>+ int err = -EINVAL;
>
>+ if (skb->len < NLMSG_LENGTH(0))
>+ goto out;
>+
>+ nlh = (struct nlmsghdr *)skb->data;
>+ msg_type = nlh->nlmsg_type;
>
>
You're introducing some kind of check for malformed packets here as
well, don't you think that such thing should be done by the receiver ?
I also see another option which is passing as parameter such function
which check for capabilities/audit stuff to my netlink_process_skb
function, calling it before process_msg. But in that case, the packet
sent by a sender that doesn't has the right to was already enqueued. I
understand that this is exactly what you are trying to avoid.
--
Pablo
next prev parent reply other threads:[~2005-02-12 16:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-12 9:01 [RFC][PATCH 0/3] netlink check sender Chris Wright
2005-02-12 9:02 ` [RFC][PATCH 1/3] " Chris Wright
2005-02-12 9:05 ` [RFC][PATCH 2/3] netlink check sender, audit Chris Wright
2005-02-12 9:06 ` [RFC][PATCH 3/3] netlink check sender, rtnetlink Chris Wright
2005-02-12 16:48 ` Pablo Neira [this message]
2005-02-12 21:41 ` [RFC][PATCH 2/3] netlink check sender, audit Pablo Neira
2005-02-14 13:08 ` Stephen Smalley
2005-02-15 0:13 ` Chris Wright
2005-02-15 2:29 ` Pablo Neira
2005-02-15 2:36 ` Pablo Neira
2005-02-15 3:47 ` Chris Wright
2005-02-15 22:19 ` Pablo Neira
2005-02-15 22:22 ` Chris Wright
2005-02-15 22:27 ` Pablo Neira
2005-02-16 0:11 ` Chris Wright
2005-02-16 3:42 ` James Morris
2005-02-15 0:11 ` Chris Wright
2005-02-14 12:59 ` [RFC][PATCH 1/3] netlink check sender Stephen Smalley
2005-02-14 13:05 ` Stephen Smalley
2005-02-15 0:22 ` Chris Wright
2005-02-15 0:17 ` Chris Wright
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=420E334B.8060805@eurodev.net \
--to=pablo@eurodev.net \
--cc=chrisw@osdl.org \
--cc=davem@davemloft.net \
--cc=jmorris@redhat.com \
--cc=netdev@oss.sgi.com \
--cc=sds@epoch.ncsc.mil \
--cc=serue@us.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.