From: Jonathan Day <imipak@yahoo•com>
To: Casey Schaufler <casey@schaufler-ca•com>
Cc: rmeijer@xs4all•nl, Samir Bellabes <sam@synack•fr>,
linux-security-module <linux-security-module@vger•kernel.org>,
Stephan Peijnik <stephan@peijnik•at>,
netdev@vger•kernel.org, netfilter-devel@vger•kernel.org
Subject: Re: RFC: Mandatory Access Control for sockets aka "personal firewalls"
Date: Wed, 21 Jan 2009 22:29:39 -0800 (PST) [thread overview]
Message-ID: <381829.34720.qm@web31504.mail.mud.yahoo.com> (raw)
In-Reply-To: <4977C4E9.1090303@schaufler-ca.com>
--- On Wed, 1/21/09, Casey Schaufler <casey@schaufler-ca•com> wrote:
> Jonathan Day wrote:
> > p.s. Which poster is going to be evil and start
> calling this Project MAC first?
> >
> Careful, it can get much worse. What about mandatory access
> controls
> based on the NIC address, not the IP address? That would be
> MAC based
> MAC. Ack.
Then I would NACK your ACK for the bigMAC MAC/MAC.
next prev parent reply other threads:[~2009-01-22 6:29 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 9:32 RFC: Mandatory Access Control for sockets aka "personal firewalls" Rob Meijer
2009-01-21 23:28 ` Peter Dolding
2009-01-22 0:50 ` Jonathan Day
2009-01-22 0:59 ` Casey Schaufler
2009-01-22 6:29 ` Jonathan Day [this message]
2009-01-22 13:46 ` Peter Dolding
2009-01-22 17:08 ` Jonathan Day
-- strict thread matches above, loose matches on Subject: below --
2009-01-21 7:25 Rob Meijer
2009-01-21 8:15 ` Peter Dolding
2009-01-21 8:35 ` Jan Engelhardt
2009-01-20 17:48 Stephan Peijnik
2009-01-20 18:24 ` Jan Engelhardt
2009-01-20 18:56 ` Stephan Peijnik
2009-01-20 20:15 ` Samir Bellabes
2009-01-20 20:31 ` Jan Engelhardt
2009-01-20 20:53 ` Paul Moore
2009-01-20 21:42 ` Samir Bellabes
2009-01-20 21:51 ` Paul Moore
2009-01-20 19:46 ` Jonathan Day
2009-01-20 21:01 ` Paul Moore
2009-01-21 0:54 ` Samir Bellabes
2009-01-21 1:18 ` Casey Schaufler
2009-01-21 3:14 ` Samir Bellabes
2009-01-20 20:47 ` Paul Moore
2009-01-20 23:48 ` Stephan Peijnik
2009-01-21 8:18 ` Samir Bellabes
2009-01-21 14:49 ` Paul Moore
2009-01-21 0:40 ` Samir Bellabes
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=381829.34720.qm@web31504.mail.mud.yahoo.com \
--to=imipak@yahoo$(echo .)com \
--cc=casey@schaufler-ca$(echo .)com \
--cc=linux-security-module@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=netfilter-devel@vger$(echo .)kernel.org \
--cc=rmeijer@xs4all$(echo .)nl \
--cc=sam@synack$(echo .)fr \
--cc=stephan@peijnik$(echo .)at \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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