From: Herbert Xu Subject: Re: Crypto Update for 2.6.38 Date: Fri, 7 Jan 2011 14:03:49 +1100 Message-ID: <20110107030349.GA845@gondor.apana.org.au> References: <20110106000157.GA16089@gondor.apana.org.au> <20110106211645.GA26184@gondor.apana.org.au> <20110106213932.GA26538@gondor.apana.org.au> <20110106223042.GA27080@gondor.apana.org.au> <20110106225301.GA27358@gondor.apana.org.au> <20110106213928.jd36vdlpcgsgcwss-cebfxv@webmail.spamcop.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Linus Torvalds , "David S. Miller" , Linux Kernel Mailing List , Linux Crypto Mailing List To: Pavel Roskin Return-path: Received: from helcar.apana.org.au ([209.40.204.226]:57256 "EHLO fornost.hengli.com.au" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755429Ab1AGDD7 (ORCPT ); Thu, 6 Jan 2011 22:03:59 -0500 Content-Disposition: inline In-Reply-To: <20110106213928.jd36vdlpcgsgcwss-cebfxv@webmail.spamcop.net> Sender: linux-crypto-owner@vger.kernel.org List-ID: On Thu, Jan 06, 2011 at 09:39:28PM -0500, Pavel Roskin wrote: > > By the way, is it a good idea to use setsockopt() this way? Some keys > may be large. And if AEAD is supported, will it use setsockopt() for > the unencrypted authenticated data? For large keys (i.e., asymmetric key crypto) the kernel keyring API would be the obvious way of passing them around. For AEAD the AD would be passed around through send/splice. Cheers, -- Email: Herbert Xu Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt