From owner-freebsd-hackers  Sat Aug  3 11:29:24 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id LAA28275
          for hackers-outgoing; Sat, 3 Aug 1996 11:29:24 -0700 (PDT)
Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA28267
          for <hackers@freebsd.org>; Sat, 3 Aug 1996 11:29:20 -0700 (PDT)
Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id MAA16287; Sat, 3 Aug 1996 12:29:11 -0600 (MDT)
Date: Sat, 3 Aug 1996 12:29:11 -0600 (MDT)
Message-Id: <199608031829.MAA16287@rocky.mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Cc: hackers@freebsd.org
Subject: Re: Anyone know how anoncvs actually works?
In-Reply-To: <1124.839074993@time.cdrom.com>
References: <1124.839074993@time.cdrom.com>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> It might be something we should set up, just to give complete coverage
> (then we could say we offered the repository via CTM, WWW, sup, cvsup,
> FTP and anoncvs - how many more options could one want? ;-).
> 
> Anyway, I'd like to find out what's involved first since the security
> implications of what little I've been able to puzzle out seem fuzzy.

I *think* they have a special 'anoncvs' account that uses a version of
cvs which disables all operations that would change the repository.


Nate