From: Paul Moore <paul.moore@hp.com>
To: casey@schaufler-ca.com
Cc: Andrew Morton <akpm@linux-foundation.org>,
davem@davemloft.net, jmorris@namei.org, mingo@elte.hu,
sds@tycho.nsa.gov, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: + smack-unlabeled-outgoing-ambient-packets.patch added to -mm tree
Date: Fri, 8 Feb 2008 12:43:52 -0500 [thread overview]
Message-ID: <200802081243.52504.paul.moore@hp.com> (raw)
In-Reply-To: <20080207120459.d4994f44.akpm@linux-foundation.org>
> > > ------------------------------------------------------
> > > Subject: Smack: unlabeled outgoing ambient packets
> > > From: Casey Schaufler <casey@schaufler-ca.com>
> > >
> > > Smack uses CIPSO labeling, but allows for unlabeled packets by
> > > specifying an "ambient" label that is applied to incoming
> > > unlabeled packets. Because the other end of the connection may
> > > dislike IP options, and ssh is one know application that behaves
> > > thus ...
I forgot to mention this earlier, but RHEL/Fedora/Rawhide has a patched
version of SSH (see RH bugzilla #202856 for the discussion/patch) that
fixes the problem of IPv4 options causing SSH to reject the connection.
It turns out that SSH is being a bit overzealous (rejecting all IPv4
options) in trying to reject source-routed packets.
--
paul moore
linux security @ hp
prev parent reply other threads:[~2008-02-08 17:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200802071901.m17J1lAY016751@imap1.linux-foundation.org>
[not found] ` <200802071450.41529.paul.moore@hp.com>
2008-02-07 20:04 ` + smack-unlabeled-outgoing-ambient-packets.patch added to -mm tree Andrew Morton
2008-02-07 20:14 ` Paul Moore
2008-02-08 1:34 ` David Miller
2008-02-08 1:54 ` Paul Moore
2008-02-08 2:15 ` David Miller
2008-02-08 2:21 ` Paul Moore
2008-02-08 1:33 ` David Miller
2008-02-08 17:43 ` 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=200802081243.52504.paul.moore@hp.com \
--to=paul.moore@hp.com \
--cc=akpm@linux-foundation.org \
--cc=casey@schaufler-ca.com \
--cc=davem@davemloft.net \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=netdev@vger.kernel.org \
--cc=sds@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).