From: hiroaki.fuse@ymail.ne.jp
To: linux-audit@redhat.com
Subject: audit library license
Date: Tue, 31 Jan 2023 09:55:20 +0900 (JST) [thread overview]
Message-ID: <1814878736.609807.1675126520174.JavaMail.yahoo@mail.yahoo.co.jp> (raw)
In-Reply-To: 1814878736.609807.1675126520174.JavaMail.yahoo.ref@mail.yahoo.co.jp
Dear All members,
We can find following lines in audit/README file
LICENSE
=======
The audit daemon is released as GPL'd code. The audit daemon's libraries
libaudit.* and libauparse.* are released under LGPL so that it may be
linked with 3rd party software.
I found that latest audit library linked libaucommon.so.
./lib/Makefile.in:AM_CPPFLAGS = -I. -I${top_srcdir} -I${top_srcdir}/auparse -I${top_srcdir}/common ./lib/Makefile.in:libaudit_la_LIBADD = $(CAPNG_LDADD) ${top_builddir}/common/libaucommon.la
./lib/Makefile.in:libaudit_la_DEPENDENCIES = $(libaudit_la_SOURCES) ../config.h ${top_builddir}/common/libaucommon.la
./auparse/Makefile.am:AM_CPPFLAGS = -I. -I${top_srcdir} -I${top_srcdir}/src -I${top_srcdir}/lib -I${top_srcdir}/common ./auparse/Makefile.am:libauparse_la_LIBADD = ${top_builddir}/lib/libaudit.la ${top_builddir}/common/libaucommon.la
./auparse/Makefile.am:libauparse_la_DEPENDENCIES = $(libauparse_la_SOURCES) ${top_builddir}/config.h ${top_builddir}/common/libaucommon.la
Libaucommo.so is created by following files
./common/Makefile.am:libaucommon_la_SOURCES = audit-fgets.c strsplit.c
And the license of audit/common/audit-fgets.c is GPLv2
This mean the license of latest audit libraries are also GPLv2.
Is my understanding correct?
--
Linux-audit mailing list
Linux-audit@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-audit
next parent reply other threads:[~2023-01-31 13:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1814878736.609807.1675126520174.JavaMail.yahoo.ref@mail.yahoo.co.jp>
2023-01-31 0:55 ` hiroaki.fuse [this message]
2023-01-31 15:53 ` audit library license Steve Grubb
[not found] <1446618833.679148.1675231237246.JavaMail.yahoo.ref@mail.yahoo.co.jp>
2023-02-01 6:00 ` 布施 博明
2023-02-01 22:08 ` Steve Grubb
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=1814878736.609807.1675126520174.JavaMail.yahoo@mail.yahoo.co.jp \
--to=hiroaki.fuse@ymail.ne.jp \
--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;
as well as URLs for NNTP newsgroup(s).