From: Ingo Molnar <mingo@elte.hu>
To: Casey Schaufler <casey@schaufler-ca.com>
Cc: David Miller <davem@davemloft.net>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [bisected] Re: [bug] networking broke, ssh: connect to port 22: Protocol error
Date: Thu, 7 Feb 2008 12:44:44 +0100 [thread overview]
Message-ID: <20080207114444.GA387@elte.hu> (raw)
In-Reply-To: <657224.72762.qm@web36615.mail.mud.yahoo.com>
* Casey Schaufler <casey@schaufler-ca.com> wrote:
> > So unlike some other security modules like SELINUX, enabling SMACK
> > breaks un-aware userspace and breaks TCP networking?
> >
> > I dont think that's expected behavior - and i'd definitely like to
> > enable SMACK in automated tests to check for regressions, etc.
>
> As Stephen mentions later, Smack uses CIPSO. sshd does not like any IP
> options because of traceroute, and must be built with that check
> disabled with the current Smack version. I have been looking at using
> unlabeled packets for the "ambient" label, it appears that doing so
> would make life simpler. I will get right on it.
ok - feel free to send me any patches to test.
Ingo
prev parent reply other threads:[~2008-02-07 11:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-06 11:38 [bug] networking broke, ssh: connect to port 22: Protocol error Ingo Molnar
2008-02-06 11:42 ` David Miller
2008-02-06 12:22 ` Ingo Molnar
2008-02-06 12:32 ` David Miller
2008-02-06 13:11 ` Ingo Molnar
2008-02-06 13:35 ` [bisected] " Ingo Molnar
2008-02-06 13:55 ` Stephen Smalley
2008-02-06 15:58 ` Casey Schaufler
2008-02-07 11:44 ` Ingo Molnar [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=20080207114444.GA387@elte.hu \
--to=mingo@elte.hu \
--cc=casey@schaufler-ca.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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).