From: Miloslav Trmac Subject: Re: RFC: Crypto API User-interface Date: Tue, 7 Sep 2010 10:54:24 -0400 (EDT) Message-ID: <28410754.1087391283871264222.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com> References: <20100907145127.GA13027@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: Herbert Xu , Linux Crypto Mailing List , netdev@vger.kernel.org To: Christoph Hellwig Return-path: Received: from mx4-phx2.redhat.com ([209.132.183.25]:51282 "EHLO mx02.colomx.prod.int.phx2.redhat.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1757087Ab0IGOy3 (ORCPT ); Tue, 7 Sep 2010 10:54:29 -0400 In-Reply-To: <20100907145127.GA13027@infradead.org> Sender: linux-crypto-owner@vger.kernel.org List-ID: ----- "Christoph Hellwig" wrote: > On Tue, Sep 07, 2010 at 10:34:25AM -0400, Miloslav Trmac wrote: > > - Don't use a FD for associated data that is limited to 16? bytes > > > > - Don't use file descriptors for input data at all, if it makes the > interface so complex. > > Calling into the kernel for 16 bytes of crypto is a braindead idea to > start with. To preve3nt idiots like you 1) It was Herbert who used AEAD as an example 2) That's how AEAD works: One large input stream, one very small. Mirek