All of lore.kernel.org
 help / color / mirror / Atom feed
From: "布施 博明" <hfuse@yahoo.co.jp>
To: "linux-audit@redhat.com" <linux-audit@redhat.com>
Cc: "hiroaki.fuse@ymail.ne.jp" <hiroaki.fuse@ymail.ne.jp>
Subject: Re: Re: audit library license
Date: Wed, 1 Feb 2023 15:00:37 +0900 (JST)	[thread overview]
Message-ID: <1446618833.679148.1675231237246.JavaMail.yahoo@mail.yahoo.co.jp> (raw)
In-Reply-To: 1446618833.679148.1675231237246.JavaMail.yahoo.ref@mail.yahoo.co.jp

Hello,

Thank you for the comment.
I also find following commit.
  - https://github.com/linux-audit/audit-userspace/commit/e63a8b1628170151016470075396e3697dd57a9b

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

Regardss,

> ----- Original Message -----
> 
> 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>
> Date: 2023/02/01 水 00:53
> Subject: Re: audit library license
> 
> 
> Hello,
> 
> On Monday, January 30, 2023 7:55:20 PM EST hiroaki.fuse@ymail.ne.jp wrote:
> > 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?
> 
> The intention stated in the README file is correct. The code in question is 
> only used by 3 plugins which are GPL and those functions are hidden from 
> external users of libaudit. The code can be relicenced to make it LGPL so 
> everything matches the intentions.
> 
> -Steve
> 
> 
> --
> Linux-audit mailing list
> Linux-audit@redhat.com
> https://listman.redhat.com/mailman/listinfo/linux-audit
> 
> 

--
Linux-audit mailing list
Linux-audit@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-audit

       reply	other threads:[~2023-02-01  6:03 UTC|newest]

Thread overview: 3+ 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 ` 布施 博明 [this message]
2023-02-01 22:08   ` audit library license Steve Grubb
2023-02-02  5:25     ` hiroaki.fuse

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=1446618833.679148.1675231237246.JavaMail.yahoo@mail.yahoo.co.jp \
    --to=hfuse@yahoo.co.jp \
    --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.