-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I misunderstood the location that is used by ssh. It appears that ssh is
invoked first and then cvsd, so there is no need for $CVSDHOME/.ssh/ -
just regular SSH account and $HOME/.ssh will do.
So you are using ssh to access a repository provided by cvsd? What would
be the benefit of using cvsd in such a setup over directly accessing the
repository over ssh (using the ext method)?
The extra protection that cvsd buys you in such a setup would be minimal
IMO. It adds some authentication checks but that could also be added with
proper file permissions on the repository and proper group membership.
If you want to directly access the repository over ssh, do something like
this [1] on the client:
export CVS_RSH=ssh
cvs -d remotehost:/path/to/repository co module
On the server you just need the proper system users and the directory
holding the repository.
[1] http://ch.tudelft.nl/~arthur/cvsd/faq.html#ssh
- --
- -- arthur - [EMAIL PROTECTED] - http://people.debian.org/~adejong --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFC+dX2VYan35+NCKcRAhedAJ0fDuqIndLEz4m2Kt/C4PCIYUi86QCdH6Js
iJ4F72wY78OBUrvurkhCR+o=
=jo3c
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
