public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: "Retallack, Mark" <mark.retallack@siemens.com>
To: "'Michael Bergandi'" <mbergandi@gmail.com>,
	       "'eCos Developer List'"	<ecos-devel@ecos.sourceware.org>
Subject: RE: On Porting OpenSSL v1.0.0c
Date: Tue, 14 Dec 2010 08:08:00 -0000	[thread overview]
Message-ID: <C4E8D0478C3D194FA02B65678CBB6C6087A78E6E66@DEFTHW99EC5MSX.ww902.siemens.net> (raw)
In-Reply-To: <AANLkTi=3hSnicTZ77Ci3Nfw9BEMYYv3Cg4Ub_kpA12QD@mail.gmail.com>

Hi, 

I have updated the original OpenSSL v0.9.6b to a later version (0.9.8o), which was released in June 2010. It has been on my todo list to get it cleaned up and generate a patch. If you are interested in that version, I can tar.gz the files and send them to you.  

Mark

-----Original Message-----
From: ecos-devel-owner@ecos.sourceware.org [mailto:ecos-devel-owner@ecos.sourceware.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 offer
guidance along the way, please let me know and we can collaborate.

Thanks for you interest and comments,

--
Mike

-- 
Michael Bergandi

      reply	other threads:[~2010-12-14  8:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-13 16:17 Michael Bergandi
2010-12-14  8:08 ` Retallack, Mark [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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=C4E8D0478C3D194FA02B65678CBB6C6087A78E6E66@DEFTHW99EC5MSX.ww902.siemens.net \
    --to=mark.retallack@siemens.com \
    --cc=ecos-devel@ecos.sourceware.org \
    --cc=mbergandi@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

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