Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 14 Dec 2000 10:26:20 -0700
From:      Warner Losh <imp@village.org>
To:        Will Andrews <will@physics.purdue.edu>
Cc:        Peter Pentchev <roam@FreeBSD.org>, ports@FreeBSD.org, kris@FreeBSD.org, security-officer@FreeBSD.org
Subject:   Re: cvs commit: ports/databases/gigabase distinfo 
Message-ID:  <200012141726.KAA48452@harmony.village.org>
In-Reply-To: Your message of "Thu, 14 Dec 2000 12:21:57 EST." <20001214122157.G1873@puck.firepipe.net> 
References:  <20001214122157.G1873@puck.firepipe.net>  <200012141225.eBECPn385434@freefall.freebsd.org> 

next in thread | previous in thread | raw e-mail | index | archive | help
In message <20001214122157.G1873@puck.firepipe.net> Will Andrews writes:
: On Thu, Dec 14, 2000 at 04:25:49AM -0800, Peter Pentchev wrote:
: >   Log:
: >   Forced commit: the previous checksum chase commit was because the source
: >   tarball changed.  No functional differences, only some prototyp definitions
: >   were changed from C preprocessor macros to real C/C++ keywords.
: >   
: >   Requested by:	kris (and SOP)
: >   Pointy hat:	roam - I *did* remember that ftp.FreeBSD.org still carried
: >   		the old distfile to diff against, but I remembered *after*
: >   		the commit (and minutes later, was reminded of the same by
: >   		several people)
: 
: As a general rule, I see little point to noting the differences between
: checksums.. most users will never know what your commit message about
: this "problem" said, since most users don't read cvs commit messages.
: Additionally, if the authors don't bother to document why they changed
: the distribution without updating the version, then it's probably not
: worth upgrading the port.

Actually, I see a good reason for noting it.  In the past there have
been sites that have been compromized and the new checksum alerted
people to the trojan.  That's why we need to make sure that when
checksums change, they are on purpose.  Noting that fact in the commit 
log (but maybe not to the level of detail) is prudent and saves the SO 
from having to wonder if we've just introduced a trojan into our
system.

Warner


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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200012141726.KAA48452>