RE: Open Cryptographic Framework (OCF) Interface for eCos

["Christophe Coutand" <ccoutand@stmi.com>]

Hi,

We came across a similar problem few months ago. At that time I consider
writing a simple eCos IO layer that could handle multiple encryption
types but with only one consumer for each to make it simple. In the end
we ended up using the crypto engine without generic IO layer...

I have not looked at the details but the OCF core seems a good
alternative and the code is pretty self content (crypto.c) which should
make it easy to port.

Christophe

-----Original Message-----
From: ecos-devel-owner@ecos.sourceware.org
[mailto:ecos-devel-owner@ecos.sourceware.org] On Behalf Of Michael
Bergandi
Sent: 9. desember 2010 19:10
To: eCos Developer List
Subject: Open Cryptographic Framework (OCF) Interface for eCos

Hi all,

I am using ecos on a product that requires encryption. Our processor has
encryption engine hardware that we are going to leverage as much as
possible. The problem we found was that there really was no good place
to put the interface to our crypto engine in ecos. This is where OCF
comes
in.

Our current thought is that we could build out an OCF interface at the
io
layer in ecos. That would provide a common interface to various crypto
engines across many platforms. Hence, an application that uses crypto
that makes use of the OCF interface would be portable to any other
board that ecos is running on that may have a different engine, but
still
provides the same crypto functionality as needed by the app.

In the future, I see many crypto libs having to adopt some common
interface
to take advantage of hardware crypto engines. OCF seems to have good
momentum.

I would like to hear some thoughts or input on the following:

1. Does the io layer sound like the right place to do this?
2. Would this work be of interest to anyone else?
3. Would this work be a candidate for being included in the ecos tree?

Other thoughts and comments welcome as well.


-- 
Michael Bergandi