From: Klaus Weidner <klaus@atsec.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: Joshua Brindle <jbrindle@tresys.com>,
Joy Latten <latten@us.ibm.com>,
Venkat Yekkirala <vyekkirala@TrustedCS.com>,
selinux@tycho.nsa.gov, paul.moore@hp.com
Subject: Re: ipsec and getpeercon()
Date: Tue, 29 Aug 2006 16:11:36 -0500 [thread overview]
Message-ID: <20060829211136.GA12307@w-m-p.com> (raw)
In-Reply-To: <1156883571.22210.225.camel@moss-spartans.epoch.ncsc.mil>
On Tue, Aug 29, 2006 at 04:32:51PM -0400, Stephen Smalley wrote:
> BTW, Joy & Venkat - it would be nice if the usage/configuration of the
> ipsec labeling was documented somewhere. I've seen emails in the past
> with sample usage, but has it been captured anywhere we can refer people
> to, like in the Fedora SELinux wiki?
I have the impression that the Fedora SELinux wiki isn't being updated
anymore since it's not editable without jumping through hoops that seem
excessive even to people working on a MLS/RBAC system...
-Klaus
--
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:[~2006-08-29 21:11 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-29 18:08 ipsec and getpeercon() Joshua Brindle
2006-08-29 18:20 ` Joshua Brindle
2006-08-29 18:28 ` Paul Moore
2006-08-29 19:28 ` Paul Moore
2006-08-29 19:37 ` Stephen Smalley
2006-08-29 19:46 ` Joshua Brindle
2006-08-29 20:25 ` Stephen Smalley
2006-08-29 20:32 ` Stephen Smalley
2006-08-29 21:11 ` Klaus Weidner [this message]
2006-08-30 11:28 ` Stephen Smalley
2006-08-29 22:37 ` Joshua Brindle
-- strict thread matches above, loose matches on Subject: below --
2006-08-30 16:43 Venkat Yekkirala
2006-09-01 12:15 ` Joshua Brindle
2006-09-01 13:16 Venkat Yekkirala
2006-09-01 13:41 ` Stephen Smalley
2006-09-01 14:35 Venkat Yekkirala
2006-09-01 15:25 ` Joshua Brindle
2006-09-01 15:40 ` Paul Moore
2006-09-04 12:59 ` Joshua Brindle
2006-09-05 3:50 ` Paul Moore
2006-09-01 15:49 Venkat Yekkirala
2006-09-01 16:52 ` Stephen Smalley
2006-09-01 17:48 ` Joshua Brindle
2006-09-01 18:17 Joy Latten
2006-09-01 19:34 Venkat Yekkirala
2006-09-01 19:41 Venkat Yekkirala
2006-09-01 19:47 Joy Latten
2006-09-01 20:19 ` Paul Moore
2006-09-04 12:43 ` Joshua Brindle
2006-09-05 3:32 ` Paul Moore
2006-09-05 11:58 ` Joshua Brindle
2006-09-05 13:31 ` Stephen Smalley
2006-09-05 13:34 ` Joshua Brindle
2006-09-05 15:24 ` Paul Moore
2006-09-05 15:22 ` Paul Moore
2006-09-01 19:52 Joy Latten
2006-09-01 20:35 Venkat Yekkirala
2006-09-04 12:38 ` Joshua Brindle
2006-09-01 20:49 Venkat Yekkirala
2006-09-01 20:58 ` Paul Moore
2006-09-01 22:32 ` Paul Moore
2006-09-04 18:51 ` Joshua Brindle
2006-09-05 4:00 ` Paul Moore
2006-09-05 11:53 ` Joshua Brindle
2006-09-05 15:15 ` Paul Moore
2006-09-01 22:42 Joy Latten
2006-09-05 14:36 Joy Latten
2006-09-05 15:43 Venkat Yekkirala
2006-09-05 16:01 ` Paul Moore
2006-09-05 16:14 Venkat Yekkirala
2006-09-05 16:27 ` Paul Moore
2006-09-05 16:27 Venkat Yekkirala
2006-09-05 16:42 Venkat Yekkirala
2006-09-05 17:10 ` Paul Moore
2006-09-05 20:01 Venkat Yekkirala
2006-09-06 15:55 ` Joshua Brindle
2006-09-05 20:04 Venkat Yekkirala
2006-09-06 16:19 Venkat Yekkirala
2006-09-06 16:20 Venkat Yekkirala
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=20060829211136.GA12307@w-m-p.com \
--to=klaus@atsec.com \
--cc=jbrindle@tresys.com \
--cc=latten@us.ibm.com \
--cc=paul.moore@hp.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
--cc=vyekkirala@TrustedCS.com \
/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.