-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
License #10
Comments
I hadn't realized the ppport issue, that was certainly not the intention. IMO the LGPL is unfortunate in this particular case, but that wasn't my choice. I'm considering replacing the AES implementation inside, which means pretty much a rewrite from scratch of most pieces I haven't rewritten already, that might actually be the cleanest way out eventually (but IANAL). |
On Wed, Sep 23, 2015 at 06:17:29AM -0700, Leon Timmermans wrote:
-- Petr |
OpenSSL may not be around on all systems, its license is a bit tricky in its own way, and Crypt-OpenSSL-AES doesn't implement the cryptographic modes (Crypt::CBC and the like add almost an order-of-magnitude in time, because they're implementing a tight loop in Perl). |
Another issue is that the |
Should be fixable: https://metacpan.org/pod/CPAN::Meta::Spec#license But its not clear what one does to disambiguate between "LGPL-2.1 only" and "LGPL-2.1+" shrug |
Lines 4 to 9 in 3ea315a
Lines 4 to 9 in 3ea315a
Lines 132 to 137 in 3ea315a
Lines 4 to 9 in 3ea315a
As-is, more files declare LGPL2.1+ than declare LGPL3. |
I'm confused regarding license that covers the Crypt-Rijndael-1.13.
Rijndael.xs states LGPLv2+.
Rijandel.pm stated LGPLv3.
ppport.h comes from perl and requires (GPL+ or Artistic).
COPYING quotes LGPLv3+.
While it's fine that each file has different license, after compiling the code and executing it, the effective license becomes GPLv3. Is that what you intended?
The text was updated successfully, but these errors were encountered: