From: Ricardo Wurmus <rekado@elephly.net>
To: ng0 <contact.ng0@cryptolab.net>
Cc: guix-devel@gnu.org
Subject: Re: bug#25356: livestreamer no longer supported
Date: Tue, 30 Jan 2018 07:47:20 +0100 [thread overview]
Message-ID: <87fu6nsv0n.fsf@elephly.net> (raw)
In-Reply-To: <20170428151839.pthpac5rsvp36e5q@abyayala>
ng0 <contact.ng0@cryptolab.net> writes:
> Leo Famulari transcribed 0.7K bytes:
>> On Wed, Jan 04, 2017 at 06:50:14PM +0000, ng0 wrote:
>> > Do I read this correctly that they include some kind of
>> > anti-military license in there? I mean I am very much welcoming
>> > such an exclusion but with all the past discussions I had it lead
>> > to the point where it is not compatible with free software.
>> >
>> > Do we have to strip OCB from the source?
>> > https://github.com/Legrandin/pycryptodome/blob/master/LICENSE.rst
>> >
>> > Pycryptodome is a dependency of streamlink.
>>
>> The question is about the OCB block cipher mode. I think we are able to
>> distribute implementations of it:
>>
>> http://web.cs.ucdavis.edu/~rogaway/ocb/ocb-faq.htm#patent:phil
>> http://web.cs.ucdavis.edu/~rogaway/ocb/ocb-faq.htm#license
>> http://web.cs.ucdavis.edu/~rogaway/ocb/license.htm
>>
>
> With regards to this bug, can someone help to get the facts clear here
> so that we know what needs to be done to package streamlink?
See also the copyright file that Debian have written:
http://metadata.ftp-master.debian.org/changelogs/main/p/pycryptodome/pycryptodome_3.4.7-1_copyright
License 1 applies to free software implementations. That’s already
enough for us.
License 2 applies to non-free implementations. There the author
distinguishes between non-military and military uses.
License 3 is an explicit grant for OpenSSL.
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
prev parent reply other threads:[~2018-01-30 6:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170104160538.GA10030@khaalida>
2017-01-04 18:50 ` bug#25356: livestreamer no longer supported ng0
2017-01-04 20:28 ` Leo Famulari
2017-04-28 15:18 ` ng0
2018-01-30 6:47 ` Ricardo Wurmus [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fu6nsv0n.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=contact.ng0@cryptolab.net \
--cc=guix-devel@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).