-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Patrick Guio <[EMAIL PROTECTED]> writes:
> I try to find some documentation about how to set up and use the
> 'cvs server' command but I cannot find that much.
> I would like to use it with ssh forced command.
cvs server is what is run in :ext: mode via $CVS_RSH and does not use
the :pserver: required option of --allow-root=<pathname>.
> Shall the '--allow-root=' option point to a $CVSROOT or can it
> directly point to a project within a $CVSROOT?
> In other words does it need access to $CVSROOT/CVSROOT?
Read access at the least if you plan to allow commits as the users will
need to be able to read the commitinfo/verifymsg/loginfo and similiar
scripts for commits as well as being able to read
$CVSROOT/CVSROOT/config
> If so how do I restrict r/w access to only one of my project when
> accessed from a special ip?
Using normal HOST access control methods.
You may find it desirable to have CVSROOT/config use a LockDir to give
different permissions for checkout than for commit.
-- Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFBfNNU3x41pRYZE/gRAqMaAJsHT+ASkcBcLzWKridY0LIwkkYzowCffhyJ
V/7sCnjtBp8g6Ec1HA4yIBs=
=Xh5I
-----END PGP SIGNATURE-----
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/info-cvs
