%META:TOPICINFO{author="RizwanKassim" date="1105856229" format="1.0" version="1.1"}% %META:TOPICPARENT{name="WebHome"}% In a fit of geekhood, I went ahead and setup a central CVS server for the lot of us to use. This way we can share our demo code, enhancements and anything we run into (via CVS and the Wiki) So, for the moment, ignore the TA's statements on how to setup CVS on your ugrad account. * Step 1 : Download [[http://www.geekymedia.com/cs103cvs.key cs103cvs.key]] and [[http://www.geekymedia.com/config config]] to your development system. * Step 2 : Copy those files into your ~/.ssh directory. (the .ssh directory in your home directory). If you have a previous config file, combine them. * Step 3 : Put the following statements into your startup script (usually .bashrc): * export CVSROOT=:ext:rizwank@67.18.44.234:/home/rizwank/cvs * export CVS_RSH=ssh * obv, if you're using cshrc, your'd modify the syntax as needed * Step 4 : Enjoy! * Now, all you have to do (once you've restarted your shell to get the new stuff that you put into your script) is write _cvs _ to import, commit, update your cvs packages! How I set it up (with reasonable security) (for reference) : SetupCVSviaSSH For Reference: Other stuff I found: http://tony.aiu.to/sa/cvs/ http://www.pizzashack.org/rssh/index.shtml b) You could provide a restricted shell on the cvs machine which only provides for the running of the 'cvs server' command and any commands that you need to run in your commitinfo/verifyinfo/loginfo/taginfo scripts. Many different kinds of restricted shells exist, which one you choose will depend almost entirely on your environment and goals. c) By forcing the /etc/ssh/rc to exec the '/usr/bin/cvs server' command for the user after always making usre the $HOME/.ssh/rc script is never allowed to exist... not really a very secure answer, but I have heard of folks using this appraoch... # $Id: WineCVS.txt,v 1.1.1.1 2005/02/12 13:09:18 rizwank Exp $ -- Main.RizwanKassim - 16 Jan 2005