From: Nikos Mavrogiannopoulos Subject: Re: communicating from the user space Date: Mon, 23 Feb 2015 09:30:14 +0100 Message-ID: References: <1424640392.22199.3.camel@gnutls.org> <1465303.BM7DbpydIc@tachyon.chronox.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Cc: sri sowj , "linux-crypto@vger.kernel.org" To: Stephan Mueller Return-path: Received: from mail-la0-f52.google.com ([209.85.215.52]:44509 "EHLO mail-la0-f52.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752160AbbBWIaQ (ORCPT ); Mon, 23 Feb 2015 03:30:16 -0500 Received: by lams18 with SMTP id s18so16897692lam.11 for ; Mon, 23 Feb 2015 00:30:14 -0800 (PST) In-Reply-To: <1465303.BM7DbpydIc@tachyon.chronox.de> Sender: linux-crypto-owner@vger.kernel.org List-ID: On Mon, Feb 23, 2015 at 9:18 AM, Stephan Mueller wrote: >> one more thing while compiling openssl with above mentioned changes I >> faced compilation issues in linux ,Please can you also let me know >> whether there are per-requisites like any dependent libraries or >> installing cryptodev-linux on host/target machine before compiling >> openssl etc? > Per default, you lack the kernel side support (there is no /dev/crypto) unless > you patch your kernel. Thus, that cryptodev support in OpenSSL is not used on > default kernels. It depends. If you are working in an embedded system /dev/crypto is most probably there. AF_ALG could be supported too, but there is little reason to use it, unless working slow is your goal. regards, Nikos