From: paul.moore@hp.com
To: netdev@vger.kernel.org, selinux@tycho.nsa.gov
Cc: jmorris@redhat.com, sds@epoch.ncsc.mil, eparis@redhat.com
Subject: [patch 0/1] NetLabel bugfix for 2.6.19
Date: Mon, 30 Oct 2006 13:03:31 -0500 [thread overview]
Message-ID: <20061030180331.404950000@hp.com> (raw)
Sorry, but another bugfix patch for NetLabel which I think should be included
2.6.19.
The problem is that the SELinux reference policy is a bit more free in allowing
applications to call setsockopt() than I had originally thought, which means
that normal applications could add or tamper with the NetLabel/CIPSO options on
a socket causing all sorts of nastiness. This patch should solve these
problems.
--
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.
WARNING: multiple messages have this Message-ID (diff)
From: paul.moore@hp.com
To: netdev@vger.kernel.org, selinux@tycho.nsa.gov
Cc: jmorris@redhat.com, sds@epoch.ncsc.mil, eparis@redhat.com
Subject: [patch 0/1] NetLabel bugfix for 2.6.19
Date: Mon, 30 Oct 2006 13:03:31 -0500 [thread overview]
Message-ID: <20061030180331.404950000@hp.com> (raw)
Sorry, but another bugfix patch for NetLabel which I think should be included
2.6.19.
The problem is that the SELinux reference policy is a bit more free in allowing
applications to call setsockopt() than I had originally thought, which means
that normal applications could add or tamper with the NetLabel/CIPSO options on
a socket causing all sorts of nastiness. This patch should solve these
problems.
--
paul moore
linux security @ hp
next reply other threads:[~2006-10-30 18:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-30 18:03 paul.moore [this message]
2006-10-30 18:03 ` [patch 0/1] NetLabel bugfix for 2.6.19 paul.moore
2006-10-30 18:03 ` [patch 1/1] NetLabel: protect the CIPSOv4 socket option from setsockopt() paul.moore
2006-10-30 18:03 ` paul.moore
2006-10-30 18:58 ` James Morris
2006-10-30 18:58 ` James Morris
2006-10-30 20:31 ` Eric Paris
2006-10-30 20:31 ` Eric Paris
2006-10-30 20:58 ` Paul Moore
2006-10-30 20:58 ` 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=20061030180331.404950000@hp.com \
--to=paul.moore@hp.com \
--cc=eparis@redhat.com \
--cc=jmorris@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=sds@epoch.ncsc.mil \
--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.