From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25697 invoked by alias); 2 May 2013 12:56:25 -0000 Mailing-List: contact ecos-maintainers-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: ecos-maintainers-owner@ecos.sourceware.org Received: (qmail 25687 invoked by uid 89); 2 May 2013 12:56:24 -0000 X-Spam-SWARE-Status: No, score=-3.3 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.1 Received: from hagrid.ecoscentric.com (HELO mail.ecoscentric.com) (212.13.207.197) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Thu, 02 May 2013 12:56:23 +0000 Received: from localhost (hagrid.ecoscentric.com [127.0.0.1]) by mail.ecoscentric.com (Postfix) with ESMTP id BAD0D4680005; Thu, 2 May 2013 13:56:21 +0100 (BST) Received: from mail.ecoscentric.com ([127.0.0.1]) by localhost (hagrid.ecoscentric.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fTDFfENkAzKI; Thu, 2 May 2013 13:56:16 +0100 (BST) Received: from [192.168.1.100] (farm.ecoscentric.com [62.249.226.156]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: paulb@ecoscentric.com) by mail.ecoscentric.com (Postfix) with ESMTP id C435A4680003; Thu, 2 May 2013 13:56:16 +0100 (BST) Message-ID: <5182626F.6090802@ecoscentric.com> Date: Thu, 02 May 2013 12:56:00 -0000 From: Paul Beskeen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5 MIME-Version: 1.0 To: Sergei Gavrikov CC: ecos-maintainers@ecos.sourceware.org Subject: Fwd: [ECOS] Re: PolarSSL for eCos References: In-Reply-To: X-Forwarded-Message-Id: Content-Type: multipart/mixed; boundary="------------020407080407070307050107" X-Virus-Found: No X-SW-Source: 2013-05/txt/msg00000.txt.bz2 This is a multi-part message in MIME format. --------------020407080407070307050107 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-length: 2176 Sergei and other maintainers, IANAL, but I don't think that the PolarSSL FOSS exception is that useful in the eCos context - eCos itself might be OK is my read - but certainly not any developer's proprietary embedded application that it is linked with. I think you should carefully consider the licensing aspects here before making this an official eCos project. Regards, Paul. -- -------- Original Message -------- Subject: [ECOS] Re: PolarSSL for eCos Date: Thu, 2 May 2013 14:14:31 +0300 (FET) From: Sergei Gavrikov To: Max Seidenstücker CC: eCos Discuss Hi Max, [Added eCos Discuss to CC] On Thu, 2 May 2013, Max Seidenstücker wrote: > Hi Sergei, > > I am writing you because I saw posts that you successfully ported > PolarSSL to eCos already. > > For a research project we are currently using eCos and need a TLS1.2 > secured connection. So therefore we need to either update OpenSSL form > 0.9.6b to 1.0.1, which seems pretty difficult or find an alternative > SSL library. > > PolarSSL looks really promising, as it also has less ressource usage > than OpenSSL. > > I am very curious on how far you have come with the porting. That was a weekend hack only. As far I call correctly the porting process was straightforward, that GPL PolarSSL version had a few I/O stubs to overwrite and I have got HTTPS connection on eCos synthetic target. I had no further work with PolarSSL (and SSL for eCos) but, IMHO, the project was very promising SSL project ... and IT IS as thanking your e-mail I knew that PolarSSL team became to provide FOSS License Exception https://polarssl.org/foss-license-exception IANAL, but it looks like that we would use GPL PolarSSL 2.0 with that FOSS exception in eCos. If this so, you would register new eCos project http://ecos.sourceware.org/contrib.html open eCos Bugzilla entry (http://bugs.ecos.sourceware.org) for the port and I hope you will find more hands for porting process then. But before to start I would get confirmation that PolarSSL FOSS License exception does cover the eCos License exception. Sergei --------------020407080407070307050107 Content-Type: text/plain; charset=windows-1252; name="Attached Message Part" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="Attached Message Part" Content-length: 149 -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss --------------020407080407070307050107--