linux-kernel - Re: linux-next: manual merge of the audit tree with the powerpc tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAHC9VhTcV6jn4z7uGXZb=RZ5k7W4KW1vnoAUMHN6Zhkxsw1Xpg@mail.gmail.com>
Date:   Thu, 16 Dec 2021 18:04:47 -0500
From:   Paul Moore <paul@...l-moore.com>
To:     Christophe Leroy <christophe.leroy@...roup.eu>
Cc:     Cédric Le Goater <clg@...d.org>,
        Stephen Rothwell <sfr@...b.auug.org.au>,
        Richard Guy Briggs <rgb@...hat.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        PowerPC <linuxppc-dev@...ts.ozlabs.org>
Subject: Re: linux-next: manual merge of the audit tree with the powerpc tree

On Thu, Dec 16, 2021 at 4:08 AM Christophe Leroy
<christophe.leroy@...roup.eu> wrote:
> Thanks Cédric, I've now been able to install debian PPC32 port of DEBIAN
> 11 on QEMU and run the tests.
>
> I followed instructions in file README.md provided in the test suite.
> I also modified tests/Makefile to force MODE := 32
>
> I've got a lot of failures, am I missing some options in the kernel or
> something ?
>
> Running as   user    root
>          with context root:::
>          on   system

While SELinux is not required for audit, I don't think I've ever run
it on system without SELinux.  In theory the audit-testsuite shouldn't
rely on SELinux being present (other than the SELinux specific tests
of course), but I'm not confident enough to say that the test suite
will run without problem without SELinux.

If it isn't too difficult, I would suggest enabling SELinux in your
kernel build and ensuring the necessary userspace, policy, etc. is
installed.  You don't need to worry about getting it all running
correctly; the audit-testsuite should pass with SELinux in permissive
mode.

If you're still seeing all these failures after trying that let us know.

> # Test 3 got: "256" (backlog_wait_time_actual_reset/test at line 151)
> #   Expected: "0"
> #  backlog_wait_time_actual_reset/test line 151 is: ok( $result, 0 );
>   # Was an event found?

...

-- 
paul moore
www.paul-moore.com