From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: GPL-less alternatives to the Audit Userland
Date: Mon, 20 Aug 2012 18:55:18 -0400 [thread overview]
Message-ID: <1603825.UxS3QBnQ69@x2> (raw)
In-Reply-To: <CACkDPNd9etK7qAAyZnfeUmTMhGMexmSWC-jYJU08tOo1p-k5=A@mail.gmail.com>
On Monday, August 20, 2012 02:33:36 PM Nathaniel Husted wrote:
> For a while I've been working on a project that ports/forks Audit to
> the Android platform (https://github.com/nwhusted/AuditdAndroid). I
> currently have a proof of concept in operation and I am working on
> getting the relevant kernel code back-patched and the userland code
> integrated in Android. One of the primary issues raised at the moment
> is the Android Open Source Project code base is not compatible with
> GPL code. I am currently unaware of any userland audit interface that
> is not under the GPL. I was wondering if anyone on the list knew of
> any, if they even exist? Any information is much appreciated.
libaudit is under LGPL which gives you as much latitude as Glibc. The Linux
kernel itself is GPLv2. So, what's the problem with GPL on Android?
-Steve
next prev parent reply other threads:[~2012-08-20 22:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-20 21:33 GPL-less alternatives to the Audit Userland Nathaniel Husted
2012-08-20 22:55 ` Steve Grubb [this message]
2012-08-20 23:06 ` Nathaniel Husted
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1603825.UxS3QBnQ69@x2 \
--to=sgrubb@redhat.com \
--cc=linux-audit@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox