[cvsnt] Windows 2000 File Permissions and remote access protocols

[Jim B.]

Hi Glen,

You're right. The file system permissions granted to the SYSTEM user were
insufficient.  I changed these for both SYSTEM and "cvsuser." pserver is now
working fine.

I next tried the ntserver method and ran into a bit of trouble; I didn't
realize that the writers file (not just file system permissions) affected
user access. After adding cvsuser and Administrator to the writers file, I
was able to execute:

cvs - d :ntserver:theta:d:\cvsrepo\test2 passwd -a cvsuser

without incident.

(Before editing the writers file, I got an error message indicating that the
specified user did not have write permission on the repository.)

I also commented out the SystemAuth=yes line in the config file. (This seems
to affect ntserver as well, though I'm not quite sure in what manner.)

I read your SetACLS article; this was tremendously helpful (Section 1.4.2 is
where I learned the dependency of the ntserver method on the writers file -
thanks!).

I've also downloaded your SetACLS.cmd script.

Thanks once again for your kind assistance (and your article!).

Yours truly,
Jim Bonang



"Glen Starrett" <grstarrett at cox.net> wrote in message
news:mailman.29.1060728630.590.cvsnt at cvsnt.org...
> > I followed Bo Berglund's excellent CVSNT Installation
> > Background for the most part, but creating the repository
> > under the Administrator account is evidently not a common approach.
>
> I don't believe that is true at all--I think most people have installed
> and created their repositories under the adminitrator account.  It is
> possible though that if you locked down the permissions on the cvsnt /
> repository / temp directories that you neglected to grant permissions to
> the SYSTEM account.  Usually the SYSTEM account has access via MS'
> "generous" everyone read access but that is sometimes removed.  Did you
> check that SYSTEM had permissions on the files?
>
> Regards,
>
> Glen Starrett
>