From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932381AbcFCKMT (ORCPT ); Fri, 3 Jun 2016 06:12:19 -0400 Received: from helcar.hengli.com.au ([209.40.204.226]:49640 "EHLO helcar.hengli.com.au" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751808AbcFCKMS (ORCPT ); Fri, 3 Jun 2016 06:12:18 -0400 Date: Fri, 3 Jun 2016 18:12:05 +0800 From: Herbert Xu To: Stephan Mueller Cc: Marcus Meissner , davem@davemloft.net, linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: authenc methods vs FIPS in light of unencrypted associated data Message-ID: <20160603101205.GA31461@gondor.apana.org.au> References: <20160602160104.GK18490@suse.de> <2641743.LA46gJhHTE@tauon.atsec.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2641743.LA46gJhHTE@tauon.atsec.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jun 03, 2016 at 08:42:31AM +0200, Stephan Mueller wrote: > > Herbert, when using crypto_spawn_*, is there a flag set by the crypto API that > the to-be-instantiated cipher is invoked by the kernel crypto API instead of > by a user? I would assume that the INTERNAL flag could be of relevance here. > If that INTERNAL flag is set, I think that the function alg_test could be > changed such that if the INTERNAL flag is set, the fips_allowed flag is not > enforced. Yes we can certainly set INTERNAL for this case. Thanks, -- Email: Herbert Xu Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt