Subject: Re: /rescue/* currently does not seem to link without patentented crypo algorithms
To: Steven M. Bellovin <smb@cs.columbia.edu>
From: Frank Kardel <kardel@acm.org>
List: current-users
Date: 01/21/2005 07:46:55
On Thu, Jan 20, 2005 at 05:00:42PM -0500, Steven M. Bellovin wrote:
> In message <20050119012146.GL23234@mewburn.net>, Luke Mewburn writes:
> >
> >--yOCDj6dCdxu1mn4c
> >Content-Type: text/plain; charset=us-ascii
> >Content-Disposition: inline
> >Content-Transfer-Encoding: quoted-printable
> >
> >On Wed, Jan 19, 2005 at 09:21:38AM +1100, I wrote:
> >  | The problem here appears to be that your build of rescue/ssh is trying
> >  | to build with kerberos contrary to what the rescue build is trying to d=
> >o.
> >  |=20
> >  | Do you build with any MKxxx or USE_xxx variables overridden ?
> >
> >Please try revision 1.18 of distrib/common/Makefile.crunch as
> >it fixes the problem where you pass MKKERBEROS=3Dyes via make(1)'s
> >command line, which was overriding rescue/Makefile's use of
> >CRUNCHENV+=3DMKKERBEROS=3Dno.
> >
> 
> I have 1.18; I'm seeing the same error.  I don't believe I have any 
> relevant entries in mk.conf
> 
> 		--Prof. Steven M. Bellovin, http://www.cs.columbia.edu/~smb
> 
Well after I got 1.18 (and the other stuf the came with it) the problem
went away. My current CRYPTO related MK*-type defines are:

MKCRYPTO=yes

MKCRYPTO_RSA=yes

MKKERBEROS=yes

Frank