Linux-audit Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: Richard Fontana <rfontana@redhat.com>
Cc: linux-audit@redhat.com
Subject: Re: Licensing of libaudit and libauparse
Date: Mon, 20 Mar 2017 11:48:07 -0400	[thread overview]
Message-ID: <1998000.GV3LKLYfuP@x2> (raw)
In-Reply-To: <20170320031304.GA4113@clifford>

On Sunday, March 19, 2017 11:13:04 PM EDT Richard Fontana wrote:
> On Sun, Mar 19, 2017 at 01:54:52PM -0400, Steve Grubb wrote:
> > On Saturday, March 18, 2017 11:32:14 PM EDT Richard Fontana wrote:
> > > Hi,
> > > 
> > > The README file in the audit userspace package says:
> > >   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.
> > > 
> > > However don't these libraries contain code from this file
> > > https://github.com/linux-audit/audit-userspace/blob/master/lib/strsplit.
> > > c
> > > which states its license is GPLv2+?
> > 
> > Yes, that looks like a copy and paste mistake. Thanks for pointing that
> > out. Anything in:
> > 
> > https://github.com/linux-audit/audit-userspace/blob/master/lib/
> > https://github.com/linux-audit/audit-userspace/blob/master/auparse/
> > https://github.com/linux-audit/audit-userspace/blob/master/bindings/
> > 
> > is intended to LGPL. Would replacing the comment at the beginning of the
> > file be sufficient to fix this issue?
> 
> It may depend on the history of the file. If you were the only person
> who contributed to it, yes. But if anyone else contributed to it, and
> let's say the contributions were not copyrighted by Red Hat, and the
> contributions were sufficiently nontrivial, then maybe we'd have to
> get permission from such other contributors to change the indicated
> license of the file.

OK. Good to know. I am the sole contributor to that file. I also checked and 
fixed some new files in auparse/ to which I am also the sole contributor at the 
same time. Everything is good in git and the next release should take care of 
this issue.

Thanks for noticing this.

-Steve

  reply	other threads:[~2017-03-20 15:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-19  3:32 Licensing of libaudit and libauparse Richard Fontana
2017-03-19 17:54 ` Steve Grubb
2017-03-20  3:13   ` Richard Fontana
2017-03-20 15:48     ` Steve Grubb [this message]
2017-03-20 20:14       ` Richard Fontana

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=1998000.GV3LKLYfuP@x2 \
    --to=sgrubb@redhat.com \
    --cc=linux-audit@redhat.com \
    --cc=rfontana@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