From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steve Grubb Subject: Re: [PATCH 1/1]: ipsec audit Date: Thu, 2 Nov 2006 17:57:00 -0500 Message-ID: <200611021757.00565.sgrubb@redhat.com> References: <1161908598.17737.280.camel@faith.austin.ibm.com> <200610301201.30040.sgrubb@redhat.com> <1162422628.17737.298.camel@faith.austin.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1162422628.17737.298.camel@faith.austin.ibm.com> Content-Disposition: inline List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-audit-bounces@redhat.com Errors-To: linux-audit-bounces@redhat.com To: Joy Latten Cc: linux-audit@redhat.com List-Id: linux-audit@redhat.com On Wednesday 01 November 2006 18:10, Joy Latten wrote: > Ok, I see how to get the security id from the netlink packet, but how do > I get it from the audit context? Look at the function audit_log_task_context(). You can use it probably. > > > ctx_alg=%d ctx_doi=%d > > > > I'd drop the ctx in favor of sp. > > ok, but since the algorithm and doi or specific to security lsm/selinux > and not ipsec, would sec_alg, or sec_doi, be better? Sure. -Steve