From: Stephen Smalley <sds@tycho.nsa.gov>
To: Mark Webb <elihusmails@gmail.com>
Cc: selinux@tycho.nsa.gov
Subject: Re: labeled network aware kernel
Date: Thu, 30 Apr 2009 08:01:11 -0400 [thread overview]
Message-ID: <1241092871.27331.3.camel@localhost.localdomain> (raw)
In-Reply-To: <9f066ee90904292005i282d1339ld060cd90fa9e9dae@mail.gmail.com>
On Wed, 2009-04-29 at 23:05 -0400, Mark Webb wrote:
> I am working to get the labelled IPSec working, following Josh
> Brindle's blog post
> (http://securityblog.org/brindle/2007/05/28/secure-networking-with-selinux).
> I just want to get the client and server running on loopback, using a
> fully patched Fedora 10 machine.
>
> I have the following keyfile that I pass into setkey:
> ----------
> spdflush;
>
> flush;
>
> spdadd 127.0.0.1 127.0.0.1 any
> -ctx 1 1 "system_u:object_r:default_t:s0"
> -P in ipsec esp/transport//require;
>
> spdadd 127.0.0.1 127.0.0.1 any
> -ctx 1 1 "system_u:object_r:default_t:s0"
> -P out ipsec esp/transport//require;
> ----------
>
> I enter the following commands:
>
> --- Terminal 1 ---
> setenforce 0
> setkey -f <keyfile>
> ./server
>
> --- Terminal 2 ---
> # ./client 127.0.0.1
> getpeercon: Protocol not available
> Received: Hello, (null) from (null)
>
> --- Terminal 1 ---
> getsockopt: Protocol not available
> server: got connection from 127.0.0.1, (null)
>
> Not sure what I am missing. I have installed ipsec-tools and started
> /etc/init.d/racoon.
>
> Any help would be appreciated.
IPSEC and loopback don't generally get along very well. Try:
echo 0 > /proc/sys/net/ipv4/conf/lo/disable_policy
echo 0 > /proc/sys/net/ipv4/conf/lo/disable_xfrm
Might want to also read through an old bug report on this issue,
https://bugzilla.redhat.com/show_bug.cgi?id=218386
--
Stephen Smalley
National Security Agency
--
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.
next prev parent reply other threads:[~2009-04-30 12:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-22 11:26 labeled network aware kernel Mark Webb
2009-04-22 15:41 ` Xavier Toth
2009-04-22 22:16 ` Paul Moore
2009-04-23 3:05 ` Mark Webb
2009-04-23 16:33 ` Paul Moore
2009-04-22 22:21 ` Chad Sellers
2009-04-23 3:01 ` Mark Webb
2009-04-24 21:44 ` Joy Latten
2009-04-30 3:05 ` Mark Webb
2009-04-30 3:45 ` Justin P. Mattock
2009-04-30 11:16 ` Mark Webb
2009-04-30 12:01 ` Stephen Smalley [this message]
2009-04-30 17:42 ` Justin Mattock
2009-05-01 3:39 ` Mark Webb
2009-05-01 4:23 ` Justin Mattock
2009-05-01 4:06 ` Mark Webb
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=1241092871.27331.3.camel@localhost.localdomain \
--to=sds@tycho.nsa.gov \
--cc=elihusmails@gmail.com \
--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.