From owner-freebsd-current Sun Aug 11 15:08:00 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA15529 for current-outgoing; Sun, 11 Aug 1996 15:08:00 -0700 (PDT) Received: from mail.crl.com (mail.crl.com [165.113.1.22]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA15524 for ; Sun, 11 Aug 1996 15:07:58 -0700 (PDT) Received: from ctasim.com by mail.crl.com with SMTP id AA10369 (5.65c/IDA-1.5 for ); Sun, 11 Aug 1996 15:06:54 -0700 Received: by deepthought.ctasim.com (940816.SGI.8.6.9/920502.SGI.AUTO) id PAA01727; Sun, 11 Aug 1996 15:49:56 -0600 From: jon@ctasim.com ("Jon Doran" ) Message-Id: <9608111549.ZM1725@deepthought.ctasim.com> Date: Sun, 11 Aug 1996 15:49:54 -0600 In-Reply-To: John Polstra "Re: Irrelevant comments on cvsup" (Aug 9, 9:18pm) References: <199608100418.VAA24857@austin.polstra.com> X-Mailer: Z-Mail (3.2.0 26oct94 MediaMail) To: John Polstra Subject: Re: Irrelevant comments on cvsup Cc: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk John, I've been running 2.0.5R since its release, and only recently have had the time to play with -current. Since I'm new to the mailing lists I'm lurking around, rather than jumping in and causing trouble :-) I haven't had a chance to play with cvsup yet, I just got sup working through our firewall last weekend... On that note: You can either generate the checksums during off hours from a cron job, or build them up as things change. As you pointed out, there are always people who backdoor changes in. I think there are ways to deal with this problem. First, consider people who dump things into the tree via RCS or CVS. Lets use RCS, since its a lower common denominator. It would be useful to place hooks in RCS to run filters at various stages of the ci and co process. For example, a site may have standards on the format of code in the tree, so part of the ci process might involve running indent on all code to convert it into the standard format. Part of the co process might involve running indent again, to convert it into a developer's favorite format. CVS users may wish to have RCS run a "filter" which updates the MD5 checksum database on checkin. Now, for those who backdoor in changes, or restore from backup tape. A cron job could scan the CVS tree looking for new files, update the database, and send nasty mail to the CVS administrator. So I think a solution is possible. In summary, there are two missing pieces. A change to RCS, and a scanning daemon. Jon Doran