From owner-freebsd-current Thu Sep 25 11:56:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA05129 for current-outgoing; Thu, 25 Sep 1997 11:56:43 -0700 (PDT) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA05104 for ; Thu, 25 Sep 1997 11:56:26 -0700 (PDT) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.8.7/8.8.7) with ESMTP id UAA07638; Thu, 25 Sep 1997 20:56:29 +0200 (SAT) Received: from greenpeace.grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.8.7/8.8.7) with ESMTP id UAA09180; Thu, 25 Sep 1997 20:56:18 +0200 (SAT) Message-Id: <199709251856.UAA09180@greenpeace.grondar.za> X-Mailer: exmh version 2.0zeta 7/24/97 To: Brandon Gillespie cc: freebsd-current@FreeBSD.ORG Subject: Re: where to place new crypt() files? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 25 Sep 1997 20:56:11 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Brandon Gillespie wrote: > lib/libcrypt/blowfish.c Isn't Blowfish export-restricted? > And the file: > > lib/libcrypt/crypt-des.c Also? > In addition to the -DDES_CRYPT flag to make is all that is required to > include DES crypt in the brew. I really don't think duplicating all of > the above files in both lib/libcrypt and secure/src/lib/libcrypt is a good > idea... Good point. > Any suggestions? The cleanest solution (imho) would be to have > secure/src/lib/libcrypt/[Makefile|crypt-des.c], and have the Makefile > create a softlink from secure/src/lib/libcrypt/crypt-des.c to > lib/libcrypt, then move to the lib/libcrypt directory and 'make > -DDES_CRYPT' Symlinks are not a good idea. Why do you not (ab)use .PATH: to find either the real or failing that a dummy crypt-des.c routine? M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org