From owner-freebsd-current Mon Apr 6 11:50:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA07396 for freebsd-current-outgoing; Mon, 6 Apr 1998 11:50:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from kong.dorms.spbu.ru (kong@kong.dorms.spbu.ru [195.19.252.147]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA07358 for ; Mon, 6 Apr 1998 11:50:19 -0700 (PDT) (envelope-from kong@kong.spb.ru) Received: from localhost (kong@localhost) by kong.dorms.spbu.ru (8.8.8/kong/0.01) with SMTP id WAA13770; Mon, 6 Apr 1998 22:49:29 +0400 (MSD) (envelope-from kong@kong.spb.ru) Date: Mon, 6 Apr 1998 22:49:28 +0400 (MSD) From: Hostas Red X-Sender: kong@kong.dorms.spbu.ru To: Lutz Albers cc: current@FreeBSD.ORG Subject: Re: Communicator 4.05 doesn't installs with 128bit security In-Reply-To: <35291981.3C39FD8A@muc.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! On Mon, 6 Apr 1998, Lutz Albers wrote: > > 'make -DUSE_128BIT install' fail after installing all files, but before > > ==== Fortify 1.2.1; Copyright (C) 1997,1998 Farrell McKay ==== > Isn't that obvious ? Fortify 1.2.1 doesn't know this netscape version > (yet), so it can't patch it for 128-bit encryption. So take out the > fortify step till a new version is released :-) That's what i did at first. :) Adios, /KONG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message