Date: Thu, 8 Dec 2005 16:39:12 +0000 From: RW <list-freebsd-2004@morbius.sent.com> To: freebsd-questions@freebsd.org Subject: Re: MD5 discrepancy in 6.0-RELEASE/src/CHECKSUM.MD5 Message-ID: <200512081639.14249.list-freebsd-2004@morbius.sent.com> In-Reply-To: <bbe90d1d0512080233m3a4e2468r82519a38d4c92b98@mail.gmail.com> References: <20051208051410.GA21908@ns.museum.rain.com> <bbe90d1d0512080233m3a4e2468r82519a38d4c92b98@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday 08 December 2005 10:33, Svein Halvor Halvorsen wrote: > On 12/8/05, James Long <list@museum.rain.com> 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200512081639.14249.list-freebsd-2004>