The purpose of this page
This page is intended for use in collecting recipes that complement the existing documentation on using CVS on W3C servers with user contributed instructions on how to set up existing tools to establish a working environment with W3C CVS servers through ssh.
See also Tantek Çelik W3C CVS For Dummies.
Note: CVS is only recommended for expert users. If you would prefer to use a simpler interface to edit pages on the Web site, consider WebDAV.
SSH Key notes
SSH keys used for W3C access MUST be in the SSH 2 protocol format. There is existing documentation describing how to generate new keys. See SSH Tutorial for Linux (and Mac OS) and SSH Tutorial for Windows for instance.
CVS Client Software
Disclaimer: W3C does not keep a list of current CVS clients. The information we provide here is added as it becomes available and is updated periodically as newer information is reported. There is a well-maintained list of clients on the Ximbiot site. You may want to compare the various available SSH clients to select the best one for your needs.
On most Unix (linux) machines, cvs is included and you can use it as a command line tool. If it was not the case on your system, you can download cvs from GNU Web site.
One of the main hurdles to running CVS on Windows was that SSH was not natively supported. However, starting with the Windows 10 April Update, deployed in April-May 2018, the OpenSSH library is now included in Windows and typically available in the
C:\Windows\System32\OpenSSH\ folder. As a result, to use CVS as a command line tool on a Windows system, all you have to do is to download and install cvs for Windows from the GNU Web site.
Beware when setting the
RSH_SSH environment variable though, the OpenSSH distribution is 64-bit only, whereas the latest version of the cvs command-line interface is 32-bit. If the
RSH_SSH variable points to the
System32 folder, Windows will automatically redirect that to the
SysWOW64 folder, which contains 32-bits versions of executables but does not contain OpenSSH (why
System32 contains 64-bit versions whereas
SysWOW64 contains 32-bit version is anyone's guess), and CVS will fail to run SSH. To force the use of the 64-bits version of SSH, you should set
%SYSTEMROOT%\Sysnative\OpenSSH\ssh.exe (alternatively, you can copy the
ssh.exe executable to some other folder that does not have weird automated redirection rules).
SmartCVS is a multi-platform CVS GUI client.
In the following we assume you have already generated an SSH RSA pubkey pair (2048 bits minimum key length).
To make SmartCVS work with SSH, follow these steps:
- Launch SmartCVS and select "Check out project from repository"
- Under "Repository profile: Manage..." and press "manage", then "add"
- Under General Options:
- choose access method: ext (SSH1.SSh2) and checkbox use: ssh: prefix.
- user-name: your-w3c-account-name
- server name: cvs.w3.org
- repository path: /w3ccvs
- Press next and move on to configuration:
- Authentication: public/private key
- Choose private key file (the one generate with Putty earlier on
- Add passphrase (if you don't want to type it each time
- ssh-type to use: ssh2
- Prefered public key: rsa
- Verify connection when pressing next
- After pressing next you should see the fingerprint for cvs.s3.org (either of these)
TortoiseCVS (deprecated, use SmartCVS instead)
TortoiseCVS lets you work with files under CVS version control directly from Windows Explorer. To make TortoiseCVS work with SSH, follow these steps:
- Open the TortoiseCVS settings and go to the "Tools" tab
- Look for the row "SSH Application (only :ext:)" and make sure that "C:\Program Files\TortoiseCVS\TortoisePlink.exe" is specified there (or the directory where you have installed TortoiseCVS)
- Set your public key:
- a) If you are using Putty's Pageant then add the (Putty) public key into Pageant and you are all set to connect to the CVS server.
- b) If you are not using Pageant then you have to specify the location of your (Putty) public key with "-i c:\path\to\your\public\key.ppk" on the row "SSH Parameters (only :ext:)" in addition to the already given parameters and then connect.
Note also Jeremy's mail to configure putty.
To set up a specific server / repository, see Richard's instructions
Note: In my experience (Feb 2009), setting environment variables alone did not work because ssh required some additional parameters, and I had to write a shell script to supply those, setting the CVS_RSH variable to point to the script: My script (called sshw3.sh) looks like this:
#!/bin/sh ssh -2 -i ~/key-name.rsa $1 $2 $3 $4 $5
(forcing protocol version 2, selecting the correct identity key and passing values from the CVS client which calls ssh) I then ran
Eclipse contains support for SSH and CVS. See Setting W3C CVS Public or Restricted Repositories for Eclipse 3.x.
Mac OS X is a unix BSD system, and then you can easily use CVS on the machine once you have installed Xcode Tools CD that accompanies Mac OS X. The manual Version Control with CVS on Mac OS X will easily guide you through the steps of using it. It means also that all Java GUI working for Unix will work Mac OS X as well.
CVL (Concurrent Versions Librarian) is a version and configuration management tool for MacOS X. CVL is a graphical user interface to CVS (Concurrent Versioning System) most often used commands.
Emacs is known to be able to do more than one thing. It is then possible to use CVS inside Emacs.
Emacs built in Version Control
Emacs has a built in Version Control system (for CVS, RCS and SCCS) system. There is no reason to leave emacs for the command prompt. Look under Tools menu, then Version Control or M-x vc- and then tab complete to see the options.