From owner-freebsd-security@FreeBSD.ORG Thu Aug 26 19:53:40 2004 Return-Path: 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 6E2F316A4CE for ; Thu, 26 Aug 2004 19:53:40 +0000 (GMT) Received: from out001.verizon.net (out001pub.verizon.net [206.46.170.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id F0CA043D2F for ; Thu, 26 Aug 2004 19:53:39 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from [192.168.1.3] ([68.160.193.218]) by out001.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20040826195339.JKAN24594.out001.verizon.net@[192.168.1.3]>; Thu, 26 Aug 2004 14:53:39 -0500 Message-ID: <412E3FBE.8080708@mac.com> Date: Thu, 26 Aug 2004 15:53:34 -0400 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040803 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-security@freebsd.org References: <293AF1C6-F73B-11D8-91E7-00039312D914@fillmore-labs.com> In-Reply-To: <293AF1C6-F73B-11D8-91E7-00039312D914@fillmore-labs.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at out001.verizon.net from [68.160.193.218] at Thu, 26 Aug 2004 14:53:39 -0500 cc: eikemeier@fillmore-labs.com Subject: Re: Report of collision-generation with MD5 X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Security issues [members-only posting] List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Aug 2004 19:53:40 -0000 Oliver Eikemeier wrote: > Mohacsi Janos wrote: >> I would also opt for having (by default) additional hash algorithms. [ ... ] >> The most easiest way would be to define a knob like >> PREFERED_HASH that would list the algorithms that system would prefer, >> and REQUIRED_HASH that would be required to checked: >> - makesum should generate all the PREFERED_HASH >> - fetch should fail if any of the REQUIRED_HASH failed makesum ought to generate all of the available hashes, otherwise what happens if someone sets REQUIRED_HASH to a hash that wasn't PREFERED? > devel/portmk supports generation of multiple hashes, although it will > just verify the first of the sufficient ones. the problem is to test > this stuff before 5.3. I installed and activated devel/portmk on a 4.10 system. I think I found the variable to control which algorithms are used, but: 48-sec# cd /usr/ports/astro/accrete 49-sec# env VALID_ALGORITHMS='MD5 SHA1 RMD160' make makesum 50-sec# cat distinfo MD5 (accrete-1.0.tar.gz) = a8586ec1682cb9545ea380d78a8e83d1 SIZE (accrete-1.0.tar.gz) = 17212 ...? -- -Chuck PS: Can I vote for a "make distinfo" target, either as an alias of "make makesum", or as dependency between the distinfo file and the actual distribution files from /usr/ports/distfiles?