From owner-freebsd-security  Sat Mar 22  5:40:28 2003
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 1602C37B404; Sat, 22 Mar 2003 05:40:26 -0800 (PST)
Received: from ms.is.s.u-tokyo.ac.jp (ms.is.s.u-tokyo.ac.jp [133.11.8.7])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id A266643F85; Sat, 22 Mar 2003 05:40:23 -0800 (PST)
	(envelope-from tsuyoshi@is.s.u-tokyo.ac.jp)
Received: from localhost (san.is.s.u-tokyo.ac.jp [133.11.28.66])
	by ms.is.s.u-tokyo.ac.jp (8.11.6+Sun/3.7W) with ESMTP id h2MDSPL11581;
	Sat, 22 Mar 2003 22:28:25 +0900 (JST)
Date: Sat, 22 Mar 2003 22:40:19 +0900 (JST)
Message-Id: <20030322.224019.112630843.tsuyoshi@is.s.u-tokyo.ac.jp>
To: freebsd-security@FreeBSD.ORG
Cc: portsmgr@FreeBSD.ORG
Subject: Re: FreeBSD Security Advisory FreeBSD-SA-03:06.openssl
From: ITO Tsuyoshi <tsuyoshi@is.s.u-tokyo.ac.jp>
In-Reply-To: <SwUKKpX9Sw@dmeyer.dinoex.sub.org>
References: <200303212052.h2LKqYWw013362@freefall.freebsd.org>
	<20030322.210923.71081935.tsuyoshi@is.s.u-tokyo.ac.jp>
	<SwUKKpX9Sw@dmeyer.dinoex.sub.org>
X-Mailer: Mew version 3.2 on Emacs 21.2 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-security@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-security.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-security>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-security>
X-Loop: FreeBSD.org

From: dirk.meyer@dinoex.sub.org (Dirk Meyer)
Date: Sat, 22 Mar 2003 14:04:43 +0100
> port is updated, but not yet committed.
> I will commit it after the freeze is lifted.
> 
> It is not as critical as the last advisory.

I see.  I was afraid that the patch for the problem (2) was completely
forgotten for the port, because no PRs were found on
  http://www.jp.freebsd.org/cgi/query-pr-summary.cgi?category=ports

> Its portsmgr decision to retag. (CC with this mail)

Sorry, I do not understand this sentence.  Maybe the portsmgr's
decision is _not_ to move the RELEASE_4_8_0 tag?

Anyway, I am releaved to know the patch is not forgotten.  Thanks for
the explanation.

Best regards,
Tsuyoshi

---   ITO Tsuyoshi  <tsuyoshi@is.s.u-tokyo.ac.jp>   ---
--- Dept. of Computer Science, University of Tokyo. ---

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message