From: Catalin Vasile Subject: Re: IV generation in cryptographic driver in AEAD Date: Wed, 18 May 2016 13:56:00 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=Windows-1252 Content-Transfer-Encoding: QUOTED-PRINTABLE To: Denis B , "linux-crypto@vger.kernel.org" Return-path: Received: from mail-am1on0100.outbound.protection.outlook.com ([157.56.112.100]:26256 "EHLO emea01-am1-obe.outbound.protection.outlook.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S932113AbcEROLo convert rfc822-to-8bit (ORCPT ); Wed, 18 May 2016 10:11:44 -0400 In-Reply-To: Content-Language: en-US Sender: linux-crypto-owner@vger.kernel.org List-ID: Inline comments. ________________________________________ =46rom: linux-crypto-owner@vger.kernel.org on behalf of Denis B Sent: Wednesday, May 18, 2016 3:06 PM To: linux-crypto@vger.kernel.org Subject: IV generation in cryptographic driver in AEAD Hello, In AEAD mode (or in any case, in IPSec ESP IPv4 =96 esp4.c), in kernel versions prior to 4.2 the cryptographic driver is expected to generate an IV. What if my driver is unable to generate an IV? [Catalin Vasile] Simple: You do not implement the givcrypt() primitive. The kernel will = generate the IV in software and then call your encrypt() primitive. Thanks, Dennis. -- To unsubscribe from this list: send the line "unsubscribe linux-crypto"= in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html