From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steve Grubb Subject: Re: [PATCH 3rd revision] Add SELinux context support to AUDIT target Date: Wed, 8 Jun 2011 14:36:38 -0400 Message-ID: <201106081436.38509.sgrubb@redhat.com> References: <4DEDEB99.4070601@netfilter.org> <201106081049.48026.sgrubb@redhat.com> <4DEFBBBE.6090307@schaufler-ca.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: Thomas Graf , linux-audit@redhat.com, netfilter-devel@vger.kernel.org, Al Viro , Eric Paris , Patrick McHardy , Pablo Neira Ayuso To: Casey Schaufler Return-path: In-Reply-To: <4DEFBBBE.6090307@schaufler-ca.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-audit-bounces@redhat.com Errors-To: linux-audit-bounces@redhat.com List-Id: netfilter-devel.vger.kernel.org On Wednesday, June 08, 2011 02:13:18 PM Casey Schaufler wrote: > On 6/8/2011 7:49 AM, Steve Grubb wrote: > > On Tuesday, June 07, 2011 06:32:35 AM Mr Dash Four wrote: > >> Add SELinux context support to AUDIT target - 3rd revision (style-type > >> changes made *only* since 2nd revision of this patch). Typical (raw > > > >> auditd) output after applying this patch would be: > > > > > >> @@ -163,6 +170,15 @@ audit_tg(struct sk_buff *skb, const struct > >> xt_action_param *par) break; > >> > >> } > >> > >> +#ifdef CONFIG_NF_CONNTRACK_SECMARK > >> + if (skb->secmark) { > >> + if (!security_secid_to_secctx(skb->secmark, &secctx, &len)) { > >> + audit_log_format(ab, " obj=%s", secctx); > >> + security_release_secctx(secctx, len); > >> + } > > > > else > > > > audit_log_format(ab, " osid=%u", skb->secmark); > > > > _All_ audit code records the number on a failed conversion. > > But it really shouldn't. An unconvertible secid is indicative > of a serious, unrecoverable failure within the LSM. It's every > bit as bad as an invalid pointer. I agree with that point. But do the LSM's panic the kernel or send an audit event that they could not convert something? Besides my patch to the patch, how is this error preserved in the audit trail? -Steve