From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12411 invoked by alias); 2 May 2013 11:14:39 -0000 Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Received: (qmail 12400 invoked by uid 89); 2 May 2013 11:14:39 -0000 X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_05,FREEMAIL_FROM,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,RCVD_IN_SORBS_WEB,SPF_PASS autolearn=ham version=3.3.1 Received: from mail-wg0-f43.google.com (HELO mail-wg0-f43.google.com) (74.125.82.43) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Thu, 02 May 2013 11:14:38 +0000 Received: by mail-wg0-f43.google.com with SMTP id c11so444945wgh.10 for ; Thu, 02 May 2013 04:14:35 -0700 (PDT) X-Received: by 10.195.13.47 with SMTP id ev15mr7241739wjd.18.1367493275704; Thu, 02 May 2013 04:14:35 -0700 (PDT) Received: from sg-laptop ([93.85.7.93]) by mx.google.com with ESMTPSA id a9sm38409206wiv.0.2013.05.02.04.14.33 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Thu, 02 May 2013 04:14:34 -0700 (PDT) Date: Thu, 02 May 2013 11:14:00 -0000 From: Sergei Gavrikov To: =?UTF-8?Q?Max_Seidenst=C3=BCcker?= cc: eCos Discuss In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="8323329-1138768882-1367491213=:2668" Content-ID: X-Virus-Found: No Subject: [ECOS] Re: PolarSSL for eCos X-SW-Source: 2013-05/txt/msg00000.txt.bz2 --8323329-1138768882-1367491213=:2668 Content-Type: TEXT/PLAIN; CHARSET=UTF-8 Content-Transfer-Encoding: 8BIT Content-ID: Content-length: 1513 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 --8323329-1138768882-1367491213=:2668 Content-Type: text/plain; charset=us-ascii Content-length: 148 -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss --8323329-1138768882-1367491213=:2668--