SSH access

( CVSSCC , VS 6.0, 1.3.x, WIN 2000/XP, UNIX )

Type: Public Status:Closed Created: 08 Apr 05 04:00 Updated: 15 Apr 05 04:00

--> Igor Pushkov (admin) at 15 Apr 05 04:00 writes

Debug dll is big overhead. Even if we will not write debug log, it
will work 10-20% slower... So the debug dll is the best solution...
May be we should announce this...

--> Tom Berg (user) at 15 Apr 05 04:00 writes

Thanks to the debug dll I could try out a few options and check the
effects. I got it to work!

There were two issues:

1) the full path to plink has to be put between quotes, otherwise command
interpretation would break off at the first space after the word Program
and plink will not start. Thus: "C:\Program Files\PuTTY\plink.exe"

2) Provide -ssh as additional SSH option

See attached screenshot fot the details.

Additional note: the private key file can be entered in either PushOK or in
PuTTY pageant. Either will work (thus you don't need pageant when you
provide the key directly to PushOK).

It would be useful to have the debug output as a Proxy option that I can
toggle.

-- Tom

CVSProxy.jpg

--> Igor Pushkov (admin) at 14 Apr 05 04:00 writes

Here it is: http://www.pushok.com/files/PushokCVSSCC_13.zip
Download zip archive, extract the dll to overwrite exiting. Repeat the
test and check the debuglog.txt near the dll. Send it to me, if
problem will be unclear.
About repeating test on our side. There is no problem to do so, but we
should make this at least with your repository, and preferable with
your private key (i not know how to manage this with SF). I.e. if you
can provide:
1. Your CVSROOT to publicly accessed server.
2. Your private key (you can change it later).
We can test this on our side. Otherwise only debug log will help.
P.S. all messages that we send to each other are logged on website. So
you always can found them here. The link exist at the top of this
letter.

--> Tom Berg (user) at 14 Apr 05 04:00 writes

Sorry, ignore my remark on the debug dll. I have spotted it in the above
messages! I plan to test it out tomorrow (as I'm currently on another
location on another machine).

-- Tom

--> Tom Berg (user) at 14 Apr 05 04:00 writes

Igor,

Somehow your email about the debug dll got lost; can you resend it?

Meanwhile I upgrade PuTTY to the latest release 0.58 and reran the tests.

- I generated a key pair (using PuTTYGen, SSH-2 DSA, 1024 bits)
- I copied the public key to SourceForge and stored the private one on my
local disk
- I checked with TortoiseCVS: works (it doesn't ask for a password for
executing the CVS command)
- Next, I entered the repository profile in PushOK and pressed the Check
button for the repository. I got a warning response: "... warning:
unrecognized response SSH-1.99-OpenSSH_3.6.1p2 from cvs server ..."

This is odd. Of course this has to do with the key-pair, but what is going
on? Any hints?

Are you able to rerun these steps yourself? And if the steps work in your
environment, can you mail me exactly what you installed/performed?

Thanks,
-- Tom

--> Igor Pushkov (admin) at 12 Apr 05 04:00 writes

Here it is:
http://www.pushok.com/files/PushokCVSSCC_13.zip
Download the zip, extract the dll to overwrite exiting. Repeat the
test and check the debuglog.txt near the dll. Send it to me, if
problem will be unclear.

--> Tom Berg (user) at 08 Apr 05 04:00 writes

Yes, please send me the debug dll. I will be out of the office for a couple
of days and will be back on Wednesday to try it out.

As for the error I am in the dark. I fill in the same repository profile as
with TortoiseCVS, but it doesn't work. The repository "/cvsroot/test1"
already exists (only the module is new), but when I press the "check"
button the window hangs. I would expect a CVSROOT OK message. See attached
screenshot for the data.

-- Tom

check.gif

--> Igor Pushkov (admin) at 08 Apr 05 04:00 writes

Yes, I can send the debug dll to produce log. You use version 1.3?
By the way, you still not write what exactly not work. You just write
that something not work. What you expect? Which error proxy shows to
you?
I have some feeling that you have some existing project under CVS,
then install plug-in and expect to see some changes opening project.
If so, please read our manual about binding to existing project.

--> Tom Berg (user) at 08 Apr 05 04:00 writes

Both CVS_RSH is set and there is a reference to plink entered in the Server
Tab.

Are there other ways I can check thing? E.g. is there an option to output
detailed trace information to find out what is going on?

-- Tom

--> Igor Pushkov (admin) at 08 Apr 05 04:00 writes

Well I not acknowledged that you use commercial version.
Seems that you make all alright, except two things. Do you:
a. Modify/add CVS_RSH environment variable to point to plink.exe?
either
b. Do you point to plink.exe at the Server options dialog?

--> Tom Berg (user) at 08 Apr 05 04:00 writes

We are using the commercial version of SourceForge (4.1), not the open
source version sourceforge.net.

The key is effective "immediate". When I upload the public key (just a
copy-paste action), I can use for example TortoiseCVS right away.

Does sourceforge.net work differently in this respect? And what type of
keys are supported?

-- Tom

--> Igor Pushkov (admin) at 08 Apr 05 04:00 writes

Source forge require some time before uploaded key will have effect.
How much time passed after you upload key?

--> Tom Berg (user) at 08 Apr 05 04:00 writes

After performing the instructions below, it still doesn't work. I create a
new VS 6.0 project and want to add this to the (existing) repository. Only
the module is new. Repository path details are filled in, but after
pressing "check" the Proxy hangs. Only option to abort is to kill the
running "cvs.exe". When I use TortoiseCVS with the same keys, everything
runs fine. The PushOk version 1.3.1-050407.

Instructions:

1. Install required materials
� PushOK
� a CVS GUI (e.g. TortoiseCVS or SmartCVS)
� PuTTY SSH suite (for PuTTYgen, Plink and Pageent)

2. Generate a key-pair and upload public key to SourceForge 4
� Start PuTTY > PuTTYgen
� Select SSH-2 DSA
� Press Generate
� Save Private key to file �pri.ppk� (just use an empty passphrase)
� Copy Pubic key to clipboard and Paste this to SourceForge > My Settings >
Authorization Keys, and press Update

3. Configure Pageant to administer your private key for SSH sessions (see
above)
� Start PuTTY > Pageant
� Double-click on the Pageant (computer with hat) icon in your system tray
� Click on the 'Add Key' button
� Select the private key file �pri.ppk� we saved during the key generation
process
� When prompted, enter the passphrase password you specified during the key
generation process, if any, then click 'Ok'.
� The key in question will now appear within Pageant's active key list.
While Pageant is running, Pageant will respond to any requests from other
PuTTY applications (such as PuTTY.EXE and PLINK.EXE) that you enter your
SSH key password
� Press Close to close the window

4. Configure PushOK Proxy
� Start PustOK Software > CVSSCC > Configure plugin
� Select Tab CVS Executables and enter:
- file-path to GUI executable (for example SmartCVS or
TortoiseCVS)� this executable will be started from the IDE (e.g. Visual C
6.0) on selecting Project > Source Control > PushOK CVS Proxy
- optionally file-path to cvs excutable
� Select Tab CVS options and check options as needed, for example:
- all options for reserved editing
- checkout files read-only
� Select Tab Server options
- fill in CVSROOT:
�:ext:username@sf1cvs.fel.tno.nl:/cvsroot/repository� where username and
repository are to be replaced by the actual value
- check RSA private key file and enter file-path to key file
- check SSH client and enter file-path to PuTTY Plink
� Press Apply and OK

5. Enable PushOKPproxy
� Start PustOK Software > CVSSCC > Switch SCC
� An application will appear in your system tray
� Right-click the icon and make sure that PushOK CVS Proxy is selected

Rate this ticket:

Not useful at all

Partially useful

Useful

Very useful

Ticket

SSH access