From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32576 invoked by alias); 9 Dec 2010 18:10:33 -0000 Received: (qmail 32567 invoked by uid 22791); 9 Dec 2010 18:10:32 -0000 X-SWARE-Spam-Status: No, hits=-1.5 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org Received: from mail-qy0-f177.google.com (HELO mail-qy0-f177.google.com) (209.85.216.177) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 09 Dec 2010 18:10:29 +0000 Received: by qyk27 with SMTP id 27so2372901qyk.15 for ; Thu, 09 Dec 2010 10:10:27 -0800 (PST) MIME-Version: 1.0 Received: by 10.224.89.75 with SMTP id d11mr6684079qam.342.1291918227216; Thu, 09 Dec 2010 10:10:27 -0800 (PST) Received: by 10.220.94.145 with HTTP; Thu, 9 Dec 2010 10:10:27 -0800 (PST) Date: Thu, 09 Dec 2010 18:10:00 -0000 Message-ID: Subject: Open Cryptographic Framework (OCF) Interface for eCos From: Michael Bergandi To: eCos Developer List Content-Type: text/plain; charset=ISO-8859-1 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/msg00004.txt.bz2 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