From: Steve Grubb <sgrubb@redhat.com>
To: "linux-audit@redhat.com" <linux-audit@redhat.com>
Cc: "hiroaki.fuse@ymail.ne.jp" <hiroaki.fuse@ymail.ne.jp>
Subject: Re: audit library license
Date: Wed, 01 Feb 2023 17:08:54 -0500 [thread overview]
Message-ID: <2683616.mvXUDI8C0e@x2> (raw)
In-Reply-To: <1446618833.679148.1675231237246.JavaMail.yahoo@mail.yahoo.co.jp>
Hello,
On Wednesday, February 1, 2023 1:00:37 AM EST 布施 博明 wrote:
> Thank you for the comment.
> I also find following commit.
> -
> https://github.com/linux-audit/audit-userspace/commit/e63a8b16281701510164
> 70075396e3697dd57a9b
>
> BTW, I found another license question.
>
> The libauparse.so are created following source codes.
>
> In 'auparse/Makefile.am'
>
> AM_CPPFLAGS = -I. -I${top_srcdir} -I${top_srcdir}/src -I${top_srcdir}/lib
> -I${top_srcdir}/common
>
> libauparse_la_SOURCES = lru.c interpret.c nvlist.c ellist.c \
> auparse.c auditd-config.c message.c data_buf.c \
> auparse-defs.h auparse-idata.h data_buf.h \
> nvlist.h auparse.h ellist.h \
> internal.h lru.h rnode.h interpret.h \
> private.h expression.c expression.h tty_named_keys.h \
> normalize.c normalize-llist.c normalize-llist.h \
> normalize-internal.h normalize_obj_kind_map.h \
> normalize_record_map.h normalize_syscall_map.h
>
> We can find following line in internal.h
>
> #include "auditd-config.h"
>
> I can find src/auditd-config.h file which is GPLv2.
>
> The "src/auditd-config.h" should be also LGPLv2.1
That file is also mislabeled. It is now corrected. Thanks for the review.
-Steve
--
Linux-audit mailing list
Linux-audit@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-audit
next prev parent reply other threads:[~2023-02-01 22:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1446618833.679148.1675231237246.JavaMail.yahoo.ref@mail.yahoo.co.jp>
2023-02-01 6:00 ` Re: audit library license 布施 博明
2023-02-01 22:08 ` Steve Grubb [this message]
2023-02-02 5:25 ` hiroaki.fuse
[not found] <1814878736.609807.1675126520174.JavaMail.yahoo.ref@mail.yahoo.co.jp>
2023-01-31 0:55 ` hiroaki.fuse
2023-01-31 15:53 ` 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=2683616.mvXUDI8C0e@x2 \
--to=sgrubb@redhat.com \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.