Re: [Firebird-devel] Re: Sourceforge WinCVS/SSH problems accessing firebird

[<pc...@at...>]

Hi Doug,

Here you are step by step instructions:

Setting up the SSH
Once you have all the files you're ready to setup your environment to 
connect to SourceForge. There's only a few things that need to be done, but 
it's important you do them or else your connection will probably not work.
I use next ssh package:
ftp://ftp.cs.hut.fi/pub/ssh/contrib/ssh-1.2.14-win32bin.zip
1. You'll need to unpack the SSH distribution files somewhere in your path. 
Either unzip them to a directory already in your path or create a new path 
and add it to your AUTOEXEC.BAT file. For example, if you put them in 
C:\BIN then add this to your AUTOEXEC.BAT file:
SET PATH=%PATH%;C:\BIN
2. You'll need a "home" directory where SSH will store settings for you. 
This can be anywhere but set it up by adding an environmental variable to 
your AUTOEXEC.BAT file like this:
SET HOMEDRIVE=C:
SET HOME=\HOME 
(or wherever you want your home directory to be)
3. You need to create an \ETC directory on the same drive you set your 
HOME directory to. In the example above, create a directory on drive C: 
called ETC.
C:
MD \ETC
4. Create a text file in this new directory called PASSWD. The file should 
have one line in it that looks something like this:
pcisar:x:1:10:Cisar, Pavel:/users/pcisar/:/windows/command.com
Each entry is separated by a colon (":"). The first entry is your SourceForge 
username. Make sure it's all in lower case. Don't worry about the next 4 
entries. The 6th entry is the path to your HOME directory you setup in step 
2. This can include a drive letter but remember to use the "/" character 
instead of the normal DOS "\". The next entry points to your command 
interpreter (command.com on Windows 95/98, cmd.exe on Windows NT). 
This isn't used but you need an entry here. 
5. Restart your system so your environmental variables and path can be 
updated.
6. You're ready to test your connection to SourceForge. From a DOS 
prompt enter the following command:
ssh -l username projectname.sourceforge.net
(for example: ssh -l pcisar nexusproject.sourceforge.net)
Replace pcisar with your SourceForge username. If this is your first time 
connecting you'll see a message saying SSH is adding the host to your 
known hosts. 
7. Enter your password at the prompt. Congratulations! You should now be 
logged into SourceForge through SSH.
---------
Now you'll need to create the SSH keypair for painless access to CVS 
server via SSH. To do that, open a command prompt and enter this to 
create a new key pair: 
ssh-keygen -C <comment> -f identity 
<comment> is an identifier placed in the public key. I used my email 
address. Just press enter when it asks you for a passphrase. You don't want 
a passphrase. BTW, without the -C option the program will fail and you 
won't get a new key pair. I couldn't use any other ssh-keygen utility except 
for this one. Any other (SecureCRT, or the linux server) and ssh.exe 
wouldn't read it. 
Next, on your user page at SourceForge, you should find a place to upload 
your SSH public key. Copy the file identity.pub (located in your .ssh 
directory) into the text entry box on the page -- be sure not to add any line 
breaks or it will not work. After the requisite 6 hour wait, you should be 
able to use CVS with SSH without using your password.

Best regards
Pavel