From: Klaus Weidner <klaus@atsec.com>
To: Joy Latten <latten@austin.ibm.com>
Cc: redhat-lspp@redhat.com, linux-audit@redhat.com,
Paul Moore <paul.moore@hp.com>
Subject: Re: auditing labeled ipsec
Date: Wed, 11 Oct 2006 17:23:46 -0500 [thread overview]
Message-ID: <20061011222345.GD28519@w-m-p.com> (raw)
In-Reply-To: <1160602996.17737.57.camel@faith.austin.ibm.com>
On Wed, Oct 11, 2006 at 04:43:16PM -0500, Joy Latten wrote:
> On Wed, 2006-10-11 at 16:58 -0400, Paul Moore wrote:
> > While it's been a looong time since I looked at PFKEY I believe you can get away
> > with plucking the loginuid from the current task, yes? no?
> >
>
> I was also wondering if that would be ok?
If it's accurate when nobody is actively trying to subvert it, that's
good enough for the purposes of LSPP/CAPP evaluation where admins are
presumed to be trustworthy.
-Klaus
next prev parent reply other threads:[~2006-10-11 22:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-11 20:40 auditing labeled ipsec Joy Latten
2006-10-11 20:58 ` Paul Moore
2006-10-11 21:43 ` [redhat-lspp] " Joy Latten
2006-10-11 22:23 ` Klaus Weidner [this message]
2006-10-12 12:36 ` Steve Grubb
2006-10-12 14:16 ` Paul Moore
2006-10-12 14:24 ` Steve Grubb
2006-10-13 21:34 ` Joy Latten
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=20061011222345.GD28519@w-m-p.com \
--to=klaus@atsec.com \
--cc=latten@austin.ibm.com \
--cc=linux-audit@redhat.com \
--cc=paul.moore@hp.com \
--cc=redhat-lspp@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox