DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <gmazyland@gmail.com>
To: dm-crypt <dm-crypt@saout.de>
Subject: [dm-crypt] [ANNOUNCE] relaxing license for cryptsetup (GPLv2 only -> GPLv2+)
Date: Sat, 29 Dec 2012 12:19:50 +0100	[thread overview]
Message-ID: <50DED1D6.7000701@gmail.com> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

next version of cryptsetup will be distributed under
"GNU General Public License as published by the Free Software Foundation;
either version 2 of the License, or (at your option) any later version"

(Previous version was GPLv2 only, so adding "or any later" part.)

This should solve problems when code is need to be used together with GPLv3.

I also changed license of some device backend sub-libraries
(crypto backend/wrapper, loopaes, verity and new tcrypt code) to use
"GNU Lesser General Public License as published by the Free Software Foundation;
either version 2.1 of the License, or (at your option) any later version".

Milan

P.S.
My intention was to change whole libcryptsetup to be covered by LGPL2.1+,
unfortunately I have no agreement from Clemens as author of LUKS code
for this particular change so libcryptsetup license (as a whole) will change
only to "GPLv2 or any later".

I do not want to delay next release 1.6 anymore because of this, there is a lot
of changes for testing already.

See also http://www.gnu.org/licenses/why-not-lgpl.en.html
(FYI I do not agree with all the arguments there personally and I think that
LGPL is better if it allows more broad use of open-formats like LUKS.)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBAgAGBQJQ3tHLAAoJENmwV3vZPpj8eR4P/26Umu5WQSGt7P0O+vJX9wF7
y+NxQUIRUXqaR55zkLg5xKi+Tz20tkvsoNpBn0gPDGhzFVAQzaZ96srr7bnPWSZZ
TpvuHcfx5EVj13RcnjdpSYnLaW/14oEeRSgUslT8TL5mpRs86bE9Bs47q8lFHm1+
tijXndHTFl9NHE2c+D3F8sHSgPehC9LEV9MwOuSVcfyu+orYMG65njYF7t9UEX11
t7fGPu4Wb7+eCWbtWDcTiEMYmsZl1TnKrByNjsbM4bLwaEL9uIRpuDcwAxPWhMvu
40/l8rkmct/X23N0rBySzRd3Oe/Zz/0wovTQKeLDDHmL4q4TLki5XAlBS0sKeDC3
88N6TY6KLuDG4ZKb4edSgruYXg/lVl3kklCXHUGiVzbPz+x8cosP9oFtbRkIT3Zg
ETiWcOMOcw+jmkxNQl0QHS4dlvX2ibTjOhOsHYx0uSpzcktQW9Q12W/YAHvfM0I7
Nmsp2fKDlyBK0zWsbYBSFZujTP+jHbpVZQekF6qkOMDIF6tThxTEq9W7J0uOl1p6
aE1W1XH9zT/d4xSFFl3BzJAQ2P6Nf2gmiYhp2OT8qlNaBxD7R4nNzr8C6iYMafmi
eikKncvCdji8qAuHji/CVif1CwJubbbM9sJVFHwU2CqtUv7X/Y+ibBXVVwgpiVqU
cnCu2apWH8WzQ3Q+ixDN
=KKEd
-----END PGP SIGNATURE-----

                 reply	other threads:[~2012-12-29 11:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=50DED1D6.7000701@gmail.com \
    --to=gmazyland@gmail.com \
    --cc=dm-crypt@saout.de \
    /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