From owner-freebsd-current Sun Sep 13 13:26:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA26566 for freebsd-current-outgoing; Sun, 13 Sep 1998 13:26:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA26555 for ; Sun, 13 Sep 1998 13:26:53 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.8.8/8.6.12) id NAA02706; Sun, 13 Sep 1998 13:26:28 -0700 (PDT) Message-ID: <19980913132628.B2429@nuxi.com> Date: Sun, 13 Sep 1998 13:26:28 -0700 From: "David O'Brien" To: Chuck Robey Cc: FreebSD Current Subject: Re: ssh port problem..... Reply-To: obrien@NUXI.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Chuck Robey on Sun, Sep 13, 1998 at 12:52:42PM -0400 X-Operating-System: FreeBSD 2.2.7-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The problem is, for the gmp and z libs, those are system libs, but the > lib callouts for them assume that they aren't system libs. The I totally agree with your patches that SSH should link with our system z and gmp libs and not those provided with the distribution. > Doing this, tho, I think might have some impact on security. I don't > know what it is. I hope maybe someone who knows security might comment. Only thing I can think of is increased security. We can link statically agaist the system libs for more security. -- -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message