From: Paul Moore <paul.moore@hp.com>
To: selinux@tycho.nsa.gov, netdev@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: Re: [RFC PATCH v2 0/7] Labeled networking patches for 2.6.28
Date: Mon, 11 Aug 2008 18:57:42 -0400 [thread overview]
Message-ID: <200808111857.42859.paul.moore@hp.com> (raw)
In-Reply-To: <20080811212640.22551.17728.stgit@flek.lan>
On Monday 11 August 2008 6:23:49 pm Paul Moore wrote:
> [NOTE: in the process of writing the examples below I found a bug in
> the 'netlabelctl cipsov4 del ...' operation, I'm looking into it
> right now but in the meantime only add :) ]
I made some stupid mistakes in netlbl_cipsov4_remove() which should now
be fixed in the git tree.
--
paul moore
linux @ hp
prev parent reply other threads:[~2008-08-11 22:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-11 22:23 [RFC PATCH v2 0/7] Labeled networking patches for 2.6.28 Paul Moore
2008-08-11 22:23 ` [RFC PATCH v2 1/7] selinux: Fix a problem in security_netlbl_sid_to_secattr() Paul Moore
2008-08-11 22:24 ` [RFC PATCH v2 2/7] netlabel: Replace protocol/NetLabel linking with refrerence counts Paul Moore
2008-08-11 22:24 ` [RFC PATCH v2 3/7] netlabel: Add a generic way to create ordered linked lists of network addrs Paul Moore
2008-08-11 22:24 ` [RFC PATCH v2 4/7] netlabel: Add network address selectors to the NetLabel/LSM domain mapping Paul Moore
2008-08-11 22:24 ` [RFC PATCH v2 5/7] netlabel: Add functionality to set the security attributes of a packet Paul Moore
2008-08-11 22:24 ` [RFC PATCH v2 6/7] selinux: Set socket NetLabel based on connection endpoint Paul Moore
2008-08-11 22:24 ` [RFC PATCH v2 7/7] selinux: Cache NetLabel secattrs in the socket's security struct Paul Moore
2008-08-11 22:57 ` Paul Moore [this message]
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=200808111857.42859.paul.moore@hp.com \
--to=paul.moore@hp.com \
--cc=linux-security-module@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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).