netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Venkat Yekkirala" <vyekkirala@trustedcs.com>
To: "'James Morris'" <jmorris@namei.org>
Cc: <netdev@vger.kernel.org>, <selinux@tycho.nsa.gov>, <sds@tycho.nsa.gov>
Subject: RE: [PATCH 2/3] mlsxfrm: Various fixes
Date: Wed, 8 Nov 2006 08:31:00 -0600	[thread overview]
Message-ID: <000501c70342$83b9df70$cc0a010a@tcssec.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0611071536300.20855@d.namei>

> > Fix SO_PEERSEC for tcp sockets to return the security context of
> > the peer (as represented by the SA from the peer) as opposed to the
> > SA used by the local/source socket.
>
> What about the case of a localhost TCP connection not using
> xfrm labeling?
>
> Joe Nall raised this as an important requirement.

Yes. We need to come up with some new ideas on this (the failed
secid-recon patchset sought to do this using the secmark field
on the skb).

The scope of this patchset is to strictly fix things related to
labeled-xfrm.
>
>
>
> (Also, 'mlsxfrm' is MLS-specific).

Will switch to "labeled-ipsec".


  reply	other threads:[~2006-11-08 14:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-07 17:17 [PATCH 2/3] mlsxfrm: Various fixes Venkat Yekkirala
2006-11-07 20:38 ` James Morris
2006-11-08 14:31   ` Venkat Yekkirala [this message]
2006-11-09  4:08     ` Paul Moore
2006-11-09  4:38       ` James Morris
2006-11-09  4:59         ` Paul Moore
2006-11-09  6:15           ` James Morris
2006-11-09  6:39             ` Paul Moore
2006-11-09  7:02               ` James Morris
2006-11-09 17:26                 ` 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='000501c70342$83b9df70$cc0a010a@tcssec.com' \
    --to=vyekkirala@trustedcs.com \
    --cc=jmorris@namei.org \
    --cc=netdev@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).