Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262109AbVDLVOL (ORCPT ); Tue, 12 Apr 2005 17:14:11 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263005AbVDLVLX (ORCPT ); Tue, 12 Apr 2005 17:11:23 -0400 Received: from electric-eye.fr.zoreil.com ([213.41.134.224]:6300 "EHLO fr.zoreil.com") by vger.kernel.org with ESMTP id S262109AbVDLVGA (ORCPT ); Tue, 12 Apr 2005 17:06:00 -0400 Date: Tue, 12 Apr 2005 23:01:52 +0200 From: Francois Romieu To: Steve French Cc: linux-kernel@vger.kernel.org, Alexander Nyberg , Jesper Juhl Subject: Re: [PATCH 1/3] cifs: md5 cleanup - functions Message-ID: <20050412210152.GB25512@electric-eye.fr.zoreil.com> References: <1113267099.5734.1.camel@smfhome.smfdom> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1113267099.5734.1.camel@smfhome.smfdom> User-Agent: Mutt/1.4.1i X-Organisation: Land of Sunshine Inc. Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1034 Lines: 23 Steve French : [...] > There was a patch suggested a year or so ago to remove the older cifs > md5 implementation and have cifsencrypt.c use the newer Linux crypto > API, but since it made the code considerably more complex it did not > make any sense. The current crypto API seems to be designed for much > more complex usage patterns than cifs needs it for. The key use for this > for CIFS is the following small function (to calculate the packet > signitures on cifs packets in fs/cifs/cifsencrypt.c) If you have the patches from 10/2003 in mind, they suffered more from poor taste than from cryptoapi imho. Btw nobody cared about fs/cifs/connect.c::CIFSNTLMSSPNegotiateSessSetup (indentation from Mars + unchecked allocations before dereferences). -- Ueimor - 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/