From: Stephen Smalley <sds@tycho.nsa.gov>
To: Joshua Brindle <brindle@quarksecurity.com>
Cc: Richard Haines <richard_c_haines@btinternet.com>,
Dominick Grift <dac.override@gmail.com>,
"selinux@tycho.nsa.gov" <selinux@tycho.nsa.gov>
Subject: Re: did libselinux grow a new build dependency? (openssl-devel: openssl.h)
Date: Tue, 20 Oct 2015 09:44:12 -0400 [thread overview]
Message-ID: <5626452C.6010806@tycho.nsa.gov> (raw)
In-Reply-To: <562644AE.3080001@quarksecurity.com>
On 10/20/2015 09:42 AM, Joshua Brindle wrote:
> Stephen Smalley wrote:
> <snip>
>>
>> Wondering if dependency on openssl might be a license issue for Debian
>> or others. Apparently openssl license is considered GPL-incompatible [1]
>> [2], and obviously libselinux is linked by a variety of GPL-licensed
>> programs. Fedora seems to view this as falling under the system library
>> exception [3] but not clear that other distributions would view it that
>> way. On the other hand, using gnutls would be subject to the reverse
>> problem; it would make libselinux depend on a LGPL library, and that
>> could create issues for non-GPL programs that statically link
>> libselinux. We might need to revert this change and revisit how to solve
>> this in a manner that avoids such issues.
>
> LGPL explicitly allows non-GPL programs to link against an LGPL licensed
> library without tainting the non-GPL program, which is the whole point
> of the LGPL. Is there some other issue with static linking or something?
Yes, that's the concern.
next prev parent reply other threads:[~2015-10-20 13:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-17 10:53 did libselinux grow a new build dependency? (openssl-devel: openssl.h) Dominick Grift
2015-10-18 12:48 ` Richard Haines
2015-10-18 14:07 ` Dominick Grift
2015-10-18 15:00 ` Richard Haines
2015-10-19 18:09 ` Stephen Smalley
2015-10-19 19:18 ` Stephen Smalley
2015-10-20 12:27 ` Richard Haines
2015-10-20 13:43 ` Stephen Smalley
2015-10-20 14:00 ` William Roberts
2015-10-20 14:39 ` Richard Haines
2015-10-20 14:49 ` William Roberts
2015-10-21 14:43 ` Richard Haines
2015-10-20 13:42 ` Joshua Brindle
2015-10-20 13:44 ` Stephen Smalley [this message]
2015-10-20 13:56 ` Joshua Brindle
2015-10-20 18:45 ` Jason Zaman
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=5626452C.6010806@tycho.nsa.gov \
--to=sds@tycho.nsa.gov \
--cc=brindle@quarksecurity.com \
--cc=dac.override@gmail.com \
--cc=richard_c_haines@btinternet.com \
--cc=selinux@tycho.nsa.gov \
/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.