Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261477AbUCIUc0 (ORCPT ); Tue, 9 Mar 2004 15:32:26 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261567AbUCIUc0 (ORCPT ); Tue, 9 Mar 2004 15:32:26 -0500 Received: from mx1.redhat.com ([66.187.233.31]:45803 "EHLO mx1.redhat.com") by vger.kernel.org with ESMTP id S261477AbUCIUcU (ORCPT ); Tue, 9 Mar 2004 15:32:20 -0500 Date: Tue, 9 Mar 2004 15:32:58 -0500 (EST) From: James Morris X-X-Sender: jmorris@thoron.boston.redhat.com To: Clay Haapala cc: Jouni Malinen , "David S. Miller" , Subject: Re: Crypto API and keyed non-HMAC digest algorithms / Michael MIC In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1094 Lines: 30 On Tue, 9 Mar 2004, Clay Haapala wrote: > On Tue, 9 Mar 2004, James Morris uttered the following: > > Agreed. I really wanted to keep digests 'pure', and not implement a > > setkey method, but it seems like the simplest way at this stage. > > > I had the same thought in my attempt at adding CRC32C to the crypto > routines, that what was needed was "digests + setkey". But I didn't > want to add the key baggage to digests, and so created a new alg type > (CHKSUM), with pretty much identical code to digest, but with a > modified init and a new setkey interface. > > So, we could modify digests now, or perhaps Jouni and I could combine > our code into a new KEYED_DIGEST type and leave digests 'pure'. > What's best? I think that adding a setkey method for digests is the simplest approach. - James -- James Morris - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/