linux-kernel - Re: linux-next: Tree for Jun 20 (kernel/auditsc.c)

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: <CAFqZXNsw8iWB74jDof39Z8KM29EDvnpvQ_AvxPbvdM9hZ1cXAQ@mail.gmail.com>
Date:   Thu, 21 Jun 2018 09:33:26 +0200
From:   Ondrej Mosnacek <omosnace@...hat.com>
To:     Paul Moore <paul@...l-moore.com>
Cc:     rdunlap@...radead.org, sfr@...b.auug.org.au,
        linux-next@...r.kernel.org,
        Linux kernel mailing list <linux-kernel@...r.kernel.org>,
        Eric Paris <eparis@...hat.com>,
        Linux-Audit Mailing List <linux-audit@...hat.com>
Subject: Re: linux-next: Tree for Jun 20 (kernel/auditsc.c)

st 20. 6. 2018 o 22:00 Paul Moore <paul@...l-moore.com> napísal(a):
>
> On Wed, Jun 20, 2018 at 11:48 AM Randy Dunlap <rdunlap@...radead.org> wrote:
> >
> > On 06/19/2018 09:42 PM, Stephen Rothwell wrote:
> > > Hi all,
> > >
> > > Changes since 20180619:
> > >
> >
> > on x86_64:
> >
> > kernel/auditsc.o: In function `audit_filter_rules.isra.20':
> > auditsc.c:(.text+0x8c5): undefined reference to `groups_search'
> > auditsc.c:(.text+0x909): undefined reference to `groups_search'
> >
> >
> > Reported-by: Randy Dunlap <rdunlap@...radead.org>
> >
> > Full randconfig file is attached.
>
> Thanks Randy.
>
> I believe the issue is that when CONFIG_MULTIUSER is not enabled
> groups.{c.o} is not included.  Ondrej, please look into this and
> submit a fix as soon as possible, thank you.

I'm working on it, stay tuned... It should be an easy fix, but it will
(likely) need changes outside the audit code. We could work around it
locally, of course, but since this is just in -next, I believe it's
worth to fix it properly.

Cheers,
--
Ondrej Mosnacek <omosnace at redhat dot com>
Associate Software Engineer, Security Technologies
Red Hat, Inc.