* Porting mbedtls (former PolarSSL) to eCos
@ 2016-01-16 11:35 Ilija Kocho
2016-01-17 21:52 ` Jonathan Larmour
0 siblings, 1 reply; 3+ messages in thread
From: Ilija Kocho @ 2016-01-16 11:35 UTC (permalink / raw)
To: ecos-maintainers; +Cc: eCos developers
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?
Ilija
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Porting mbedtls (former PolarSSL) to eCos
2016-01-16 11:35 Porting mbedtls (former PolarSSL) to eCos Ilija Kocho
@ 2016-01-17 21:52 ` Jonathan Larmour
2016-01-18 14:56 ` Ilija Kocho
0 siblings, 1 reply; 3+ messages in thread
From: Jonathan Larmour @ 2016-01-17 21:52 UTC (permalink / raw)
To: Ilija Kocho, ecos-maintainers; +Cc: eCos developers
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:
http://www.gnu.org/licenses/license-list.html#apache2
If you can overcome that somehow, then on the encryption side, first you must
check the encryption export laws of your own country. 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.
Jifl
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Porting mbedtls (former PolarSSL) to eCos
2016-01-17 21:52 ` Jonathan Larmour
@ 2016-01-18 14:56 ` Ilija Kocho
0 siblings, 0 replies; 3+ messages in thread
From: Ilija Kocho @ 2016-01-18 14:56 UTC (permalink / raw)
To: Jonathan Larmour, ecos-maintainers; +Cc: eCos developers
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:
>
> http://www.gnu.org/licenses/license-list.html#apache2
>
> 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.
Ilija
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2016-01-18 14:56 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-01-16 11:35 Porting mbedtls (former PolarSSL) to eCos Ilija Kocho
2016-01-17 21:52 ` Jonathan Larmour
2016-01-18 14:56 ` Ilija Kocho
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).