From owner-freebsd-questions@FreeBSD.ORG Thu Dec 8 16:40:13 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BBE2F16A422 for ; Thu, 8 Dec 2005 16:40:13 +0000 (GMT) (envelope-from list-freebsd-2004@morbius.sent.com) Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id B549143D93 for ; Thu, 8 Dec 2005 16:39:43 +0000 (GMT) (envelope-from list-freebsd-2004@morbius.sent.com) Received: from frontend1.internal (mysql-sessions.internal [10.202.2.149]) by frontend1.messagingengine.com (Postfix) with ESMTP id DD604D20F4D for ; Thu, 8 Dec 2005 11:39:17 -0500 (EST) Received: from frontend2.messagingengine.com ([10.202.2.151]) by frontend1.internal (MEProxy); Thu, 08 Dec 2005 11:39:17 -0500 X-Sasl-enc: K9c0NOtTU0AxwSBu9KKAojIpDYJ4pU+XxA4pGfFW8B6g 1134059957 Received: from gumby.localdomain (88-104-199-40.dynamic.dsl.as9105.com [88.104.199.40]) by frontend2.messagingengine.com (Postfix) with ESMTP id 12FF1571506 for ; Thu, 8 Dec 2005 11:39:16 -0500 (EST) From: RW To: freebsd-questions@freebsd.org Date: Thu, 8 Dec 2005 16:39:12 +0000 User-Agent: KMail/1.8.3 References: <20051208051410.GA21908@ns.museum.rain.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200512081639.14249.list-freebsd-2004@morbius.sent.com> Subject: Re: MD5 discrepancy in 6.0-RELEASE/src/CHECKSUM.MD5 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Dec 2005 16:40:13 -0000 On Thursday 08 December 2005 10:33, Svein Halvor Halvorsen wrote: > On 12/8/05, James Long wrote: > > Inside the CHECKSUM.MD5 file, however, it says that its own > > checksum should be > > > > MD5 (CHECKSUM.MD5) = 6ee62cd847afff4cadf6648389c67a11 > > This is interesting; how can the MD5 of a file be contained inside the > file itself? Or rather, how can one correctly place it there? Since > the MD5 algorithm does not converge, I would think this was > impossible. Is it not? Hopefully. The CHECKSUM.SHA256 file also contains a wrong entry for the CHECKSUM.MD5 but no entry for itself. Other directories have CHECKSUM.MD5 files which don't contain a hash for themselves. I guess an old CHECKSUM.MD5 file got included accidently.