From owner-cvs-all  Wed Oct  7 19:14:28 1998
Return-Path: <owner-cvs-all>
Received: (from daemon@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id TAA20885
          for cvs-all-outgoing; Wed, 7 Oct 1998 19:14:28 -0700 (PDT)
          (envelope-from owner-cvs-all)
Received: from friley-185-114.res.iastate.edu (friley-185-114.res.iastate.edu [129.186.185.114])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA20875;
          Wed, 7 Oct 1998 19:14:25 -0700 (PDT)
          (envelope-from ccsanady@friley-185-114.res.iastate.edu)
Received: from friley-185-114.res.iastate.edu (loopback [127.0.0.1])
	by friley-185-114.res.iastate.edu (8.9.1/8.9.1) with ESMTP id VAA07402;
	Wed, 7 Oct 1998 21:14:03 -0500 (CDT)
	(envelope-from ccsanady@friley-185-114.res.iastate.edu)
Message-Id: <199810080214.VAA07402@friley-185-114.res.iastate.edu>
X-Mailer: exmh version 2.0.2 2/24/98
To: dima@best.net
cc: asami@FreeBSD.ORG, jkh@FreeBSD.ORG, cvs-committers@FreeBSD.ORG,
        cvs-all@FreeBSD.ORG
Subject: Re: cvs commit: ports/security/ssh Makefile 
In-reply-to: Your message of "Wed, 07 Oct 1998 18:23:27 PDT."
             <199810080123.SAA28915@burka.rdy.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 07 Oct 1998 21:14:02 -0500
From: Chris Csanady <ccsanady@friley-185-114.res.iastate.edu>
Sender: owner-cvs-all@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


>Chris Csanady writes:
>> 
>> > *   Depend on ports collection rsaref, since we have it now already
>> > *   available "broken out."
>> >
>> >This doesn't look right.  When "USA_RESIDENT=YES", it already fetches
>> >and builds rsaref by itself.  If you're going to use the rsaref port,
>> >that part should be disabled.
>> 
>> Well, it fetches it--although it does not correctly build it.  It can
>> not find librsaref.a when it goes to link.   You have to rename
>> rsaref.a, and move it..
>
>No. It should use ${PREFIX}/lib/librsaref stuff.
>I have patches to ssh port to make it use rsaref2 from ports.
>Anybody care to try/review them?

I'm sure it should.  I was simply pointing out the behavior as of
a couple days ago--which in fact is broken.

Regardless, it will be nice to have this fixed.  I have wondered
though, does the ssh license preclude us from making a package
of it?  If not, it would be really nice to have available at
install time.  Perhaps with some disclaimer or something.

Chris