From: Herbert Xu Subject: [0/11] Add IV generators and givcrypt Date: Thu, 22 Nov 2007 16:47:58 +0800 Message-ID: <20071122084758.GA7536@gondor.apana.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii To: Linux Crypto Mailing List Return-path: Received: from rhun.apana.org.au ([64.62.148.172]:4611 "EHLO arnor.apana.org.au" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1750920AbXKVIsD (ORCPT ); Thu, 22 Nov 2007 03:48:03 -0500 Received: from gondolin.me.apana.org.au ([192.168.0.6] ident=mail) by arnor.apana.org.au with esmtp (Exim 4.50 #1 (Debian)) id 1Iv7j4-0008A8-VH for ; Thu, 22 Nov 2007 19:47:59 +1100 Received: from herbert by gondolin.me.apana.org.au with local (Exim 3.36 #1 (Debian)) id 1Iv7j4-0001yY-00 for ; Thu, 22 Nov 2007 16:47:58 +0800 Content-Disposition: inline Sender: linux-crypto-owner@vger.kernel.org List-Id: linux-crypto.vger.kernel.org Hi: This series of patches introduces IV generators which can be accessed through the givcrypt operation on block ciphers (other than crypto_blkcipher which should not be used for new code). The givcrypt operation is identical to encrypt except that the IV is generated by the algorithm instead of given by the user. Algorithms can either provide their own IV generator or (as most will do) use the default IV generators provided by the system. If no IV generator is specified by the system, then chainiv will be used for synchronous algorithms and eseqiv will be used for asynchronous algorithms. Counter mode algorithms (which include some stream ciphers) must choose something other than the default to ensure uniqueness for the IV. Cheers, -- Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~} Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt