Try this setting:
CVS_RSH=ssh
Assaf
Prasad Yendluri wrote:
> I am trying to get the cygwin cvs and ssh to work (like to work at the
> command level).
>
> *0. My CVS and ssh env is s follows:
> *
> CVSROOT=:ext::/cvsroot/wsbpeltc
> CVS_RSH=/bin/ssh
>
> *1. I generated keys as follow*s:
>
> $ ssh-keygen -t dsa -C
> Generating public/private dsa key pair.
> Enter file in which to save the key (/cygdrive/c//pyendluri/.ssh/id_dsa):
> Enter passphrase (empty for no passphrase):
> Enter same passphrase again:
> Your identification has been saved in /cygdrive/c/pyendluri/.ssh/id_dsa.
> Your public key has been saved in /cygdrive/c/pyendluri/.ssh/id_dsa.pub.
> The key fingerprint is:
> 50:ca:94:9c:0f:8d:43:95:2d:5b:28:74:1c:f1:fe:72
>
>
> *This generates DSA SSH2 keys.*
>
> 2. I went to the sourceforge
> http://sourceforge.net/account/editsshkeys.php
> and added the public key (as one line)
> "ssh-dss
> AAAAB3NzaC1kc3MAABCBAM4SKHgVV5vu9saamo2JXwSCNTF5cdvI7DDFtP0WmfVM3MHsfnKRnkuZM25sT7drildanINCrqjdKu3sDNZffvbseozyWSP0N2VTgoOLOPuL6403EfVlK/yWTfH2UAqNcdnAL5xq2G0cL6y90/p8Cyig7cInFCOvYv4mkLKJmVtLAAAAFQDuTj1mZtWIyPU0AL+19Bzy45UJaQAAAIEAnU3sXcX8j0PvZfM48mCjIbtQC3ZI7y8Sg6mnCYXM3AZ/rTNFhqY2AEWozkOGUMLnaIyCH+dOoe5GiClrA0RroPxWYE6Iizoyf6I7+93YJbf6upJGzyZiBL+G6JPqNYaWfiFxx43/ZGnh/+D0KRnEokWgh/KylLFZMKurpg1JACMAAACBALLeipKtdngNRLEK7SGeXigZ30CpVV9RTPivvCKPKxcnRNtxUPcuzFs4fDKVALMVshXn8H4XJ85iVi8ns2NKtXJClI/GsVw2K5w8VJlagCKSM9npvvFHhDOELBWyirriCpEIhymbPctPIqDG+IHTkOAgCwpnsd1fQ9Mglccgz+9o
> "
>
> Number of keys on the account maintenance page is shown as 1.
>
> *3. Tried to run cvs *
>
> $ cvs co -P specifications
> *cvs.exe [checkout aborted]: cannot start server via rsh: No such file
> or directory*
>
> Anyone know what could be the problem and how I can resolve this issue?
>
> Thanks.
>
> Prasad
>
> Satish Thatte wrote:
>
>>Thanks. I saw everything else you saw, but did not see the :ext: prefix
>>for the root.
>>
>>I will try this tonight.
>>
>>-----Original Message-----
>>From: Assaf Arkin [mailto:]
>>Sent: Wednesday, February 23, 2005 10:25 AM
>>To: Satish Thatte
>>Cc:
>>Subject: Re: [wsbpel-spec-edit] RE: issues for tomorrow's call
>>
>>If you're using Putty:
>>
>>Run PuttyGen to generate a new key
>>Select key type SSH2 DSA
>>Generate a new key
>>In the comment field put your login, e.g.
>>Save the private key to a file
>>Go to the account maintenance page (http://sourceforge.net/account/)
>>In the Host Access Information select SHH key edit
>>(http://sourceforge.net/account/editsshkeys.php)
>>Copy & paste the public key from the PuttyGen window as one long line
>>In the account maintenance page you will now see one key listed
>>
>>Run Pageant
>>Add the private file you saved before and the passphrase
>>Close the window
>>Pageant keeps running the background - you need pageant to run in the
>>background in order to use SSH
>>
>>Run the CVS program
>>The CVS root must be
>>:ext:<login-name>@cvs.sourceforge.net:/cvsroot/wsbpeltc
>>checkout the modules (note, the name is case sensitive) specifications
>>or UseCases
>>
>>Assaf
>>
>>
>>Satish Thatte wrote:
>>
>>
>>
>>>I figured out the CVS web location. I am imagining that the same old
>>>CVS client works with some new config.
>>>
>>>
>>>
>>>
>>------------------------------------------------------------------------
>>
>>
>>>*From:* Satish Thatte
>>>*Sent:* Tuesday, February 22, 2005 4:12 PM
>>>*To:*
>>>*Subject:* issues for tomorrow's call
>>>
>>>We have four issues to incorporate into the spec (12.1, 130, 136, 186)
>>>
>>>
>>
>>
>>
>>>and we also need to upload a new draft to the OASIS site by the next
>>>weekend. Let us discuss how much we can incorporate before the upload.
>>>
>>>Yaron seems to be implicated in all these issues except 186, which is
>>>trivial. Let us see if we can persuade him to volunteer for the lot J
>>>
>>>I have managed to log into sourceforge.net but haven't found our
>>>content. I am hoping someone else has figured this out. Let us discuss
>>>
>>>
>>
>>
>>
>>>tomorrow.
>>>
>>>The call is at the usual time and usual number etc.
>>>
>>>Satish
>>>
>>>
>>>
>>
>>
