From: Paul Moore <paul.moore@hp.com>
To: Venkat Yekkirala <vyekkirala@TrustedCS.com>
Cc: selinux@tycho.nsa.gov, jmorris@namei.org, sds@tycho.nsa.gov,
eparis@redhat.com, jbrindle@tresys.com, redhat-lspp@redhat.com
Subject: Re: [PATCH 1/1] selinux: secid reconciliation fixes V02
Date: Mon, 09 Oct 2006 12:12:52 -0400 [thread overview]
Message-ID: <452A7504.5010304@hp.com> (raw)
In-Reply-To: <36282A1733C57546BE392885C0618592015CFD4F@chaos.tcs.tcs-sec.com>
Venkat Yekkirala wrote:
>>Venkat Yekkirala wrote:
>>
>>>--- net-2.6.sid6/include/linux/security.h 2006-10-05
>>
>>12:03:39.000000000 -0500
>>
>>>+++ net-2.6/include/linux/security.h 2006-10-08
>>
>>14:10:49.000000000 -0500
>>
>>>@@ -67,6 +67,7 @@ struct xfrm_selector;
>>> struct xfrm_policy;
>>> struct xfrm_state;
>>> struct xfrm_user_sec_ctx;
>>>+struct net_device;
>>>
>>> extern int cap_netlink_send(struct sock *sk, struct sk_buff *skb);
>>> extern int cap_netlink_recv(struct sk_buff *skb, int cap);
>>>@@ -828,8 +829,8 @@ struct request_sock;
>>> * Sets the new child socket's sid to the openreq sid.
>>> * @inet_conn_established:
>>> * Sets the connection's peersid to the secmark on skb.
>>>- * @req_classify_flow:
>>>- * Sets the flow's sid to the openreq sid.
>>>+ * @igmp_classify_skb:
>>>+ * Classifies an skb representing an igmp packet.
>>
>>I wonder if it might be cleaner to have a generic
>>classify_skb() function? That
>>seems to be more inline with what James commented on earlier
>>and I'm almost
>>certain the netdev crowd would be much more open to a generic
>>hook. It
>>shouldn't be too expensive to check if the packet is an IGMP
>>packet inside the hook.
>
>
> It wouldn't necessarily be clean in that you would have to put
> all the logic to determine what kind of packet it is inside the
> hook, if it's even possible to do it under all circumstances.
Yes, but the *interface* would be cleaner which was the point I was trying to
make. There have been a lot of new LSM networking hooks introduced lately and I
thought it might be worthwhile to keep the interfaces as flexibile as possibile.
I guess we can always change it later if needed.
>>>+/*static inline void security_sk_classify_ipcm(struct sock *sk,
>>>+ struct ipcm_cookie *ipc)
>>>+{
>>>+ security_ops->sk_getsecid(sk, &ipc->secid);
>>>+}*/
>>>+
>>
>>If this really isn't needed shouldn't we just remove the code
>>altogether instead
>>of commenting it out?
>
> Yes. If you could take it out, I would appreciate it. (let me know if
> you want a new patch with this taken out).
It's probably quickest if I just drop it.
--
paul moore
linux security @ hp
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2006-10-09 16:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-09 16:01 [PATCH 1/1] selinux: secid reconciliation fixes V02 Venkat Yekkirala
2006-10-09 16:12 ` Paul Moore [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-10-09 16:51 Venkat Yekkirala
2006-10-09 15:26 Venkat Yekkirala
2006-10-09 15:51 ` Paul Moore
2006-10-09 16:48 ` Paul Moore
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=452A7504.5010304@hp.com \
--to=paul.moore@hp.com \
--cc=eparis@redhat.com \
--cc=jbrindle@tresys.com \
--cc=jmorris@namei.org \
--cc=redhat-lspp@redhat.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
--cc=vyekkirala@TrustedCS.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.