From owner-freebsd-current Wed May 28 09:44:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA20611 for current-outgoing; Wed, 28 May 1997 09:44:00 -0700 (PDT) Received: from lsd.relcom.eu.net (lsd.relcom.eu.net [193.124.23.23]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA20571; Wed, 28 May 1997 09:42:32 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by lsd.relcom.eu.net (8.8.5/8.8.5) with SMTP id UAA25006; Wed, 28 May 1997 20:42:30 +0400 (MSD) Date: Wed, 28 May 1997 20:42:28 +0400 (MSD) From: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= X-Sender: ache@lsd.relcom.eu.net To: Bill Paul cc: current@FreeBSD.ORG, markm@FreeBSD.ORG Subject: Re: Duplicate DES code in libc/rpc and secure/lib/des In-Reply-To: <199705281250.FAA09706@hub.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 28 May 1997, Bill Paul wrote: > > 2) Do we really need to duplicate the same code in several places? > > I think that secure/lib/des/rpc_* files should be removed. > > Er... by secure/lib/des, I'm assuming you mean secure/lib/libdes, > correct? If so, please tell me exactly which files contain duplicated > code. Eric Young's libdes has a _des_crypt() routine specially written > to accomodate Secure RPC, but it shouldn't contain anything in common > with the actual RPC library (other than maybe a header that describes > the structure that the RPc code passws to _des_crypt(). See secure/lib/libdes/{rpc_des.h,rpc_enc.c} It seems they can be safely removed -- Andrey A. Chernov http://www.nagual.pp.ru/~ache/