| > 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.
It's inside home LAN at separate server. But it used to be connected to the NET directly (opening 2401). I just wanted to preserve the setup as it was. NET => FW host => CVSD host | 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 Yes. This what I'm using now. Minimising the opened ports at firewall. Thank you, Jari -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
