public inbox for
 help / color / mirror / Atom feed
From: Ilija Kocho <>
To: Jonathan Larmour <>,
Cc: eCos developers <>
Subject: Re: Porting mbedtls (former PolarSSL) to eCos
Date: Mon, 18 Jan 2016 14:56:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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:
>> 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
forwarding agent.

> 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.


      reply	other threads:[~2016-01-18 14:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-16 11:35 Ilija Kocho
2016-01-17 21:52 ` Jonathan Larmour
2016-01-18 14:56   ` Ilija Kocho [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).