From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/4] python-pycryptodomex: new package
Date: Tue, 9 Oct 2018 22:19:23 +0200 [thread overview]
Message-ID: <20181009201923.GL2869@scaer> (raw)
In-Reply-To: <20181009155633.2ad54938@windsurf>
Thomas, Asaf, All,
On 2018-10-09 15:56 +0200, Thomas Petazzoni spake thusly:
> On Sat, 22 Sep 2018 22:36:28 +0300, Asaf Kahlon wrote:
> > Cryptographic library for Python
> > +PYTHON_PYCRYPTODOMEX_LICENSE = Apache-2.0
>
> I am not sure this is an accurate description of the license terms.
> Reading https://pycryptodome.readthedocs.io/en/latest/src/license.html
> (which is the same as the LICENSE.rst you use as a license file), it
> says:
>
> """
> The source code in PyCryptodome is partially in the public domain and
> partially released under the BSD 2-Clause license.
> """
>
> There is also the text of the Apache 2.0 license, but it doesn't say to
> which part of the code it applies.
It states: Apache 2.0 license (Wycheproof)
And by grepping the source tree, it seems that 'Wycheproof' is the
slef-test test harness, as we can only find it in lib/Crypto/SelfTest/
and in setup.py, supposedly to ignore warnign from said test harness, and
to list it as the data to package.
So, I think we can ignore the Apache-2.0 license, as it does not cover
stuff that goes on the target.
> And there is a special constraint for the OCB cipher, that it cannot be
> used for military purposes. I am not sure how Debian accepts that, but
> they do accept it:
> https://metadata.ftp-master.debian.org/changelogs/main/p/pycryptodome/pycryptodome_3.6.1-2_copyright.
In fact, there are 3 licenses under which OCB is made available;
http://web.cs.ucdavis.edu/~rogaway/ocb/license.htm
* License 1 ? License for Open-Source Software Implementations of OCB
(Jan 9, 2013)
* License 2 ? General License for Non-Military Software Implementations
OCB (Jan 10, 2013).
* License 3 ? Patent License for OpenSSL (Nov 13, 2013).
As far as I understand the licensing terms, OCB is available udner any
license to the choosing of the user of OCB. The pycryptodome developpers
have not choosen a license, and instead decided to propagate that choice
down to the user of pycryptodome.
> Yann, Arnout, I'm interested by your opinion on this package.
So, I would state something like:
PYTHON_PYCRYPTODOMEX_LICENSE = \
BSD-2c, \
Public Domain (pycrypto original code), \
OCB license (OCB cypher)
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2018-10-09 20:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-22 19:36 [Buildroot] [PATCH 1/4] python-pycryptodomex: new package Asaf Kahlon
2018-09-22 19:36 ` [Buildroot] [PATCH 2/4] python-ply: " Asaf Kahlon
2018-10-09 19:27 ` Thomas Petazzoni
2018-10-09 19:39 ` Yegor Yefremov
2018-10-09 19:47 ` Asaf Kahlon
2018-09-22 19:36 ` [Buildroot] [PATCH 3/4] python-pysmi: " Asaf Kahlon
2018-10-09 19:35 ` Thomas Petazzoni
2018-09-22 19:36 ` [Buildroot] [PATCH 4/4] python-pysnmp: bump to version 4.4.6 Asaf Kahlon
2018-10-09 19:37 ` Thomas Petazzoni
2018-10-09 19:54 ` Asaf Kahlon
2018-10-09 20:00 ` Thomas Petazzoni
2018-10-10 3:37 ` Asaf Kahlon
2018-10-10 12:29 ` Thomas Petazzoni
2018-10-09 13:56 ` [Buildroot] [PATCH 1/4] python-pycryptodomex: new package Thomas Petazzoni
2018-10-09 20:19 ` Yann E. MORIN [this message]
2018-10-10 21:13 ` Arnout Vandecappelle
2018-10-11 6:54 ` Thomas Petazzoni
2018-10-10 12:28 ` Thomas Petazzoni
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=20181009201923.GL2869@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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