From: "Venkat Yekkirala" <vyekkirala@TrustedCS.com>
To: "'Paul Moore'" <paul.moore@hp.com>
Cc: <selinux@tycho.nsa.gov>, <jmorris@namei.org>, <sds@tycho.nsa.gov>
Subject: RE: Labeling traffic over loopback
Date: Tue, 12 Dec 2006 11:02:37 -0600 [thread overview]
Message-ID: <000c01c71e0f$53c39da0$cc0a010a@tcssec.com> (raw)
In-Reply-To: <457EDAA1.60003@hp.com>
> > We could use an additional bit (local_label) to denote that
> > "sp" holds the source label sid (no blob, so no lifecycle mgmt).
> >
> > What do people think?
>
> Can you give an example of what the *sp value would look
> like? Are you thinking
> of adding a new field to 'sec_path' or would you create a
> sort of dummy
> 'xfrm_state' entry?
Nope. Note "(no blob, so no lifecycle mgmt)".
More specifically, we could use a union in place of sp and
when we are looking at a loopback packet and no xfrm in use
we could use the union to hold the secid.
--
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-12-12 17:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-12 16:00 Labeling traffic over loopback Venkat Yekkirala
2006-12-12 16:36 ` Paul Moore
2006-12-12 17:02 ` Venkat Yekkirala [this message]
2006-12-12 17:26 ` Paul Moore
2006-12-12 17:45 ` Venkat Yekkirala
2006-12-13 3:34 ` James Morris
2006-12-13 14:29 ` Venkat Yekkirala
2006-12-13 15:24 ` James Morris
2006-12-12 17:07 ` Joy Latten
2006-12-12 17:23 ` Casey Schaufler
-- strict thread matches above, loose matches on Subject: below --
2006-12-12 16:03 Venkat Yekkirala
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='000c01c71e0f$53c39da0$cc0a010a@tcssec.com' \
--to=vyekkirala@trustedcs.com \
--cc=jmorris@namei.org \
--cc=paul.moore@hp.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
/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.