From: David Howells Subject: Re: [PATCH 01/19] User-space API definition Date: Sun, 22 Aug 2010 11:22:47 +0100 Message-ID: <28995.1282472567@redhat.com> References: <4C6FE8A5.30309@gnutls.org> <1282293963-27807-1-git-send-email-mitr@redhat.com> <1282293963-27807-2-git-send-email-mitr@redhat.com> Cc: dhowells@redhat.com, Kyle Moffett , =?UTF-8?B?TWlsb3NsYXYgVHJtYcSN?= , Herbert Xu , linux-crypto@vger.kernel.org, Neil Horman , linux-kernel@vger.kernel.org To: Nikos Mavrogiannopoulos Return-path: Received: from mx1.redhat.com ([209.132.183.28]:32315 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752158Ab0HVKXN (ORCPT ); Sun, 22 Aug 2010 06:23:13 -0400 In-Reply-To: <4C6FE8A5.30309@gnutls.org> Sender: linux-crypto-owner@vger.kernel.org List-ID: Nikos Mavrogiannopoulos wrote: > It is not that simple. My understanding of the keyring API is that it > allows exporting of the keys to user-space and this crypto API > explicitly prevents that That's simple. Don't provide a read() key type operation, then. David