From owner-freebsd-security Tue Jul 30 9:36:36 2002 Delivered-To: freebsd-security@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8586E37B400 for ; Tue, 30 Jul 2002 09:36:33 -0700 (PDT) Received: from iota.root-servers.ch (iota.root-servers.ch [193.41.193.195]) by mx1.FreeBSD.org (Postfix) with SMTP id E8F9E43E31 for ; Tue, 30 Jul 2002 09:36:31 -0700 (PDT) (envelope-from gabriel_ambuehl@buz.ch) Received: (qmail 10467 invoked from network); 30 Jul 2002 16:36:30 -0000 Received: from dclient217-162-128-229.hispeed.ch (HELO gaxp1800) (217.162.128.229) by 0 with SMTP; 30 Jul 2002 16:36:30 -0000 Date: Tue, 30 Jul 2002 18:37:01 +0200 From: Gabriel Ambuehl X-Mailer: The Bat! (v1.60q) Educational Reply-To: gabriel_ambuehl@buz.ch Organization: BUZ Internet Services X-Priority: 3 (Normal) Message-ID: <5113861671.20020730183701@buz.ch> To: =?ISO-8859-1?B?R2VpciBS5W5lc3M=?= Cc: freebsd-security@freebsd.org Subject: Re[2]: About the openssl hole In-Reply-To: <000d01c237e5$ceede1d0$fa00a8c0@elixor> References: <004001c237cf$23c00560$fa00a8c0@elixor> <170112657687.20020730181657@buz.ch> <000d01c237e5$ceede1d0$fa00a8c0@elixor> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org -----BEGIN PGP SIGNED MESSAGE----- Hello Geir, Tuesday, July 30, 2002, 6:26:05 PM, you wrote: > I cant do that, but you could easy edit the old port your self and fix it that way. Well I tried to do that... It's just that openssl.org is practically down (you know what I mean...) and thus I was pretty much out of luck > It's your own choice what to do, if you want to risk it do so. I would have risked it (in any case, it's still better to kill SSL services myself trying to defend from the blackhats than having the blackhats destroying everything...) > If not, wait for the freebsd team to make an patch for us. That's more or less what I'm doing now. > If you take a quick look at the current branch you will se that > the openssl is changed to 0.9.6.e, but as we know, current branch aint so stable. I'll have another shot at current once the TrustedBSD stuff is in cause I really want to have ACLs ASAP but running it in production is entirely out of question right now. Best regards, Gabriel -----BEGIN PGP SIGNATURE----- Version: PGP 6.0.2i iQEVAwUBPUayoMZa2WpymlDxAQHS2wf9GgUFkA3eI2rSJlKYynsnzisode50bYdW TINnOJW/8mYYUBTiIXDLYZ6Xt+ZZhu+0LzlCQcu9XvgHnxsabDztUYAdGt/XCmde BAUysjmfoRR9FlUEjK9brovds/LKiKODoBSmN2LUSnPDUm0V0ojJbezfQPiRIEmc yHa4cKxWJoMq4gRNRTOCLr2rwVe78rbK1xw3ICe+Z0cDUzJX8VzZijKfzY39aZ9L OPSMdLQ0cJf1ASsJRthNRqzHc299oVdNbRoFia1AR9p1fpaN2u/0qu/9GxQQtYKY T4z17Enao5A8Htf2tJcWZ1/+AXkJ639/gsYUflfV7HgLruEKAwIYoA== =nLA8 -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message