From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17272 invoked by alias); 14 Dec 2010 08:08:20 -0000 Received: (qmail 17246 invoked by uid 22791); 14 Dec 2010 08:08:18 -0000 X-SWARE-Spam-Status: No, hits=2.2 required=5.0 tests=AWL,BAYES_50 X-Spam-Check-By: sourceware.org Received: from lizzard.sbs.de (HELO lizzard.sbs.de) (194.138.37.39) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 14 Dec 2010 08:08:06 +0000 Received: from mail1.sbs.de (localhost [127.0.0.1]) by lizzard.sbs.de (8.12.11.20060308/8.12.11) with ESMTP id oBE883EF009995; Tue, 14 Dec 2010 09:08:03 +0100 Received: from DEFTHW99ET2MSX.ww902.siemens.net (defthw99et2msx.ww902.siemens.net [157.163.135.163]) by mail1.sbs.de (8.13.6/8.13.6) with ESMTP id oBE883jn003689 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=FAIL); Tue, 14 Dec 2010 09:08:03 +0100 Received: from DEFTHW99EC5MSX.ww902.siemens.net ([169.254.2.233]) by DEFTHW99ET2MSX.ww902.siemens.net ([157.163.135.163]) with mapi; Tue, 14 Dec 2010 09:08:03 +0100 From: "Retallack, Mark" To: "'Michael Bergandi'" , "'eCos Developer List'" Date: Tue, 14 Dec 2010 08:08:00 -0000 Subject: RE: On Porting OpenSSL v1.0.0c Message-ID: References: In-Reply-To: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-IsSubscribed: yes Mailing-List: contact ecos-devel-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: ecos-devel-owner@ecos.sourceware.org X-SW-Source: 2010-12/txt/msg00008.txt.bz2 Hi,=20 I have updated the original OpenSSL v0.9.6b to a later version (0.9.8o), wh= ich was released in June 2010. It has been on my todo list to get it cleane= d up and generate a patch. If you are interested in that version, I can tar= .gz the files and send them to you.=20=20 Mark -----Original Message----- From: ecos-devel-owner@ecos.sourceware.org [mailto:ecos-devel-owner@ecos.so= urceware.org] On Behalf Of Michael Bergandi Sent: 13 December 2010 16:17 To: eCos Developer List Subject: On Porting OpenSSL v1.0.0c Hello all, [Disclaimer: I originally posted this on eCos-Discuss, but it got almost no response. I thought it might be better suited for this list instead. I hope= you will forgive the crosspost.] I would like to know if there is someone interested or already working on a= port of the latest OpenSSL library to eCos. If you are or know someone who is, I would love to know about it so that we are not duplicating efforts. In doing some online research regarding OpenSSL on eCos, I came across the old port of OpenSLL by Andrew Lunn that claims to be updated to the v0.= 9.6b code base. However, that port is quite dated (going on 9 years old) and the current code base is much much different now. I also came across a note from Andres in the archives in response to someone else's inquiry about using the SSL portion of the library: > Please not that i only used some of the encryption algorithms and > diffie Hellman from it. I've not used SSL. So expect it to be broken > and require some work. You may be luck and its works perfectly. > > If you do plan on update to a newer version of OpenSSL, please let me > know, i have a few suggestions.... > > Andrew Well, Andrew, if you are listening, I'm all ears... The project I am working on will be using SSL to provide a secure web interface for device configuration. In addition, we want to leverage the encryption module on our processor (mx27) to get some hardware acceleration for our other encryption needs. The ENGINE interface, in particular, is the primary reason for our desire to go ahead and port the latest OpenSSL to eCos. So, again, if anyone wants to be a part of this effort or can be there to o= ffer guidance along the way, please let me know and we can collaborate. Thanks for you interest and comments, -- Mike --=20 Michael Bergandi