On 06/25/2010 04:25 PM, Stephen Smalley wrote: > On Fri, 2010-06-25 at 16:23 -0400, Stephen Smalley wrote: >> On Fri, 2010-06-25 at 16:18 -0400, Daniel J Walsh wrote: >>> On 06/25/2010 06:30 AM, Dominick Grift wrote: >>>> On 06/25/2010 12:11 PM, Alice Mynona wrote: >>>>> Stephen Smalley schrieb am 24.06.2010 19:33 Uhr: >>>>>> On Thu, 2010-06-24 at 13:12 -0400, Stephen Smalley wrote: >>>>>>> On Thu, 2010-06-24 at 17:01 +0200, Alice Mynona wrote: >>>>>>>> Hello, >>>>>>>> >>>>>>>> during the developing of a SELinux module I got the following error messages when executing "audit2allow -a -l" >>>>>>>> >>>>>>>> ... >>>>>>>> libsepol.context_from_record: type antivirus_t is not defined >>>>>>>> libsepol.context_from_record: could not create context structure >>>>>>>> libsepol.context_from_string: could not create context structure >>>>>>>> libsepol.sepol_context_to_sid: could not convert unconfined_u:unconfined_r:antivirus_t:s0 to sid >>>>>>>> >>>>>>>> "antivirus_t" is a domain I have defined in my module: >>>>>>>> >>>>>>>> type antivirus_t; >>>>>>>> domain_type(antivirus_t) >>>>>>>> >>>>>>>> I have already removed the module (semodule -r antivirus.pp && semodule -R) and did a file context repair afterwards (fixfiles restore). The error still exists. >>>>>>>> >>>>>>>> I have reinstalled the policy (yum reinstall selinux-policy-*), but the problem remains. I have also taken a look at "file_contexts" (cd /etc/selinux/targeted/modules/active && grep antivirus_t file_contexts*), but there's no "antivirus_t" anymore. >>>>>>>> >>>>>>>> Can you help me to find the cause of the problem? I don't know how to debug libsepol-messages. >>>>>>>> >>>>>>>> I'm using "selinux-policy-targeted-3.6.32-118.fc12.noarch". >>>>>>> >>>>>>> Sounds like the -l option to audit2allow isn't working correctly, so >>>>>>> that instead of only processing audit messages since the last policy >>>>>>> reload, you are still processing the audit messages from when that >>>>>>> policy module was installed, and unsurprisingly it cannot map those >>>>>>> contexts since you removed the module. That would be a bug in >>>>>>> audit2allow/sepolgen. >>>>>>> >>>>>>> Workaround would be to use ausearch to select the desired range of >>>>>>> messsages specifically, e.g. >>>>>>> /sbin/ausearch -m AVC -ts today | audit2allow >>>>>> >>>>> >>>>> I did a reload today at 08:36:00 a.m. (semodule -R). Round about two and half hours later I checked the auditlog: >>>>> >>>>> ausearch -m AVC --start 25.06.2010 08:36:00 --end 25.06.2010 11:00:00 >>>>> >>>>> Only messages from ssh_t (success=yes). Fine. But "audit2allow -a -l" still throws error messages: >>>>> >>>>> ... >>>>> libsepol.context_from_record: type antivirus_t is not defined >>>>> libsepol.context_from_record: could not create context structure >>>>> libsepol.context_from_string: could not create context structure >>>>> libsepol.sepol_context_to_sid: could not convert unconfined_u:unconfined_r:antivirus_t:s0 to sid >>>>> ... >>>>> >>>>>> Dan - looks like you pushed the audit2why analyze calls down into >>>>>> sepolgen while it is parsing the messages. But this means that all >>>>>> messages will be analyzed even if the user specified -l. >>>>>> >>>>> >>>>> I will wait for Dan's answer :-). >>>>> >>>>> Problem solved. @All: Thanks for your help. >>>>> >>>>> Best regards, >>>>> >>>>> Alice >>>>> >>>>> p.s.: >>>>> I still don't know how to debug sepol-messages. Can you give me a hint? >>>> >>>> I think it is not just with the -l option as i had similar output today >>>> by using plain ausearch -m avc -ts recent | audit2allow: >>>> >>>> libsepol.context_from_record: invalid security context: >>>> "staff_u:staff_r:mozilla_t:s0-s0:c0.c1023" >>>> libsepol.context_from_record: could not create context structure >>>> libsepol.context_from_string: could not create context structure >>>> libsepol.sepol_context_to_sid: could not convert >>>> staff_u:staff_r:mozilla_t:s0-s0:c0.c1023 to sid >>>> libsepol.context_from_record: invalid security context: >>>> "staff_u:staff_r:mozilla_t:s0-s0:c0.c1023" >>>> >>>> >>>>> >>>>> -- >>>>> This message was distributed to subscribers of the selinux mailing list. >>>>> If you no longer wish to subscribe, send mail to majordomo@xxxxxxxxxxxxx with >>>>> the words "unsubscribe selinux" without quotes as the message. >>>> >>>> >>> Yes I want the analysis to show up in audit2allow, If libsemanage would >>> just shut up, we really should ignore the errors. >> >> Then use semanage_msg_set_callback(hnd, NULL, NULL); > > Actually I think you want sepol_msg_set_callback() since audit2why is > directly using libsepol, right? > Python does not have this binding... -- This message was distributed to subscribers of the selinux mailing list. If you no longer wish to subscribe, send mail to majordomo@xxxxxxxxxxxxx with the words "unsubscribe selinux" without quotes as the message.
