set CVS_RSH=\path\to\plink.exe
You also need to arrange to be able to connect to a remote host without any interactive prompts, as described in
section 7.2.2
.
You should then be able to run CVS as follows:
cvs -d :ext:user@sessionname:/path/to/repository co module
If you specified a username in your saved session, you don't even need to specify the ‘user’ part of this, and you can just say:
cvs -d :ext:sessionname:/path/to/repository co module
7.5 Using Plink with WinCVS
Plink can also be used with WinCVS. Firstly, arrange for Plink to be able to connect to a remote host non-interactively, as described in
section 7.2.2
.
Then, in WinCVS, bring up the ‘Preferences’ dialogue box from the Admin menu, and switch to the ‘Ports’ tab. Tick the box there labelled ‘Check for an alternate rsh name’ and in the text entry field to the right enter the full path to plink.exe. Select ‘OK’ on the ‘Preferences’ dialogue box.
Next, select ‘Command Line’ from the WinCVS ‘Admin’ menu, and type a CVS command as in
section 7.4
, for example:
cvs -d :ext:user@hostname:/path/to/repository co module
or (if you're using a saved session):
cvs -d :ext:user@sessionname:/path/to/repository co module
Select the folder you want to check out to with the ‘Change Folder’ button, and click ‘OK’ to check out your module. Once you've got modules checked out, WinCVS will happily invoke plink from the GUI for CVS operations.
Chapter 8: Using public keys for SSH authentication
•
8.1 Public key authentication - an introduction
•
8.2 Using PuTTYgen, the PuTTY key generator
o
8.2.1 Generating a new key
o
8.2.2 Selecting the type of key
o
8.2.3 Selecting the size (strength) of the key
o
8.2.4 The ‘Generate’ button
o
8.2.5 The ‘Key fingerprint’ box
o
8.2.6 Setting a comment for your key
o
8.2.7 Setting a passphrase for your key
o
8.2.8 Saving your private key to a disk file
o
8.2.9 Saving your public key to a disk file
o
8.2.10 ‘Public key for pasting into authorized_keys file’
o
8.2.11 Reloading a private key
o
8.2.12 Dealing with private keys in other formats
•
8.3 Getting ready for public key authentication
8.1 Public key authentication - an introduction
Public key authentication is an alternative means of identifying yourself to a login server, instead of typing a password. It is more secure and more flexible, but more difficult to set up.
In conventional password authentication, you prove you are who you claim to be by proving that you know the correct password. The only way to prove you know the password is to tell the server what you think the password is. This means that if the server has been hacked, or spoofed (see
section 2.2
), an attacker can learn your password.
Public key authentication solves this problem. You generate a key pair, consisting of a public key (which everybody is allowed to know) and a private key (which you keep secret and do not give to anybody). The private key is able to generate signatures. A