This is the mail archive of the
mailing list for the eCos project.
Re: Porting mbedtls (former PolarSSL) to eCos
- From: Ilija Kocho <ilijak at siva dot com dot mk>
- To: Jonathan Larmour <jifl at jifvik dot org>, ecos-maintainers at ecos dot sourceware dot org
- Cc: eCos developers <ecos-devel at ecos dot sourceware dot org>
- Date: Mon, 18 Jan 2016 15:56:27 +0100
- Subject: Re: Porting mbedtls (former PolarSSL) to eCos
- Authentication-results: sourceware.org; auth=none
- References: <569A2AFB dot 5090105 at siva dot com dot mk> <569C0D27 dot 2070907 at jifvik dot org>
On 17.01.2016 22:52, Jonathan Larmour wrote:
> On 16/01/16 11:35, Ilija Kocho wrote:
>> Hi all
>> I am porting mbedtls (former PolarSSL) Ref: https://tls.mbed.org/
>> security stack to eCos. It is now licensed under Apache 2.0 that allows
>> linking with proprietary code.
>> I would like to put patches on Bugzilla for review and discussion but
>> I'm little bit worried about regulations regarding encryption products.
>> How do I proceed?
> Unfortunately Apache 2.0 is not compatible with the GPLv2 we use:
> If you can overcome that somehow,
Perhaps this statement from eCos licence combined with GPLv3: "...either
version 2 or (at your option) any later version.".
> then on the encryption side, first you must
> check the encryption export laws of your own country.
Afaik Macedonia has no export control. Anyway I'll check with our
> Then the encryption
> export laws for the server hosting the patches, in this case the UK. I haven't
> found any good information to indicate whether it definitely does or
> definitely does not have any export control, sorry.
Then I may put EPK on some server in MK.