> >> I see (some of) the requirements as the following:
> >> 1. Allow CVS to work without a login account on the server.
> >
> >I don't understand the problem with creating an ssh account that only
> >allows the cvs server command. I certainly have more confidence in ssh's
> >security than in CVS's, and I believe this is the setup that SourceForge
> >is currently using.
>
> I should've added another requirement:
> 3. Minimize involvement of sysadmin (at least for management of read-only
> users).
>
> The reason I didn't include it the first time is 'cos it's more a requirement in
> a maintenance sense than an absolute sense. For example, I'd like to distribute
> (to an extent) the admin of the repository so that I can give authorization to
> some people to be able to add/remove other people to the list of read-only
> users.
I differ with Noel: I think that it is absolute anathema to have CVS work
without a login account on the server.
However, I agree with Noel about minimizing sysadmin involvement.
Sysadmin should only be required to set up user accounts.
The setup of the CVS project, repository, management of permissions,
etc., none of it should require sysadmin involvement.
This is one of the biggest reasons I am pro-network filesystems
and against servers.
