Authentication Window Appearing Again and Again Tortoise Svn

How to utilise SVN over SSH tunnel (svn+ssh) with PushOK SVNSCC plug-in

This instruction assumes the following things:

• you already have a user account on a Unix server;
• the user have permissions to admission to the Subversion repository, located on this server;
• you tin can admission this server using SSH.

At that place are several means of setting upward your environment to piece of work with svn+ssh:// protocol. First nosotros will describe the recommended ane, simply if information technology is not suitable for yous, in that location are some culling configurations mentioned farther.

The recommended configuration

Perform the following steps to ready up your surround.

1. TortoisePlink.exe will exist needed for SSH hallmark and tunnelling. Then you have to install TortoiseSVN (http://tortoisesvn.net/).
2. Install PuTTY - a free SSH client for Windows (http://www.chiark.greenend.org.uk/~sgtatham/putty/).
3. Become to "System properties" / "Avant-garde" / "Surround Variables..." and create theSVN_SSH variable which points to TortoisePlink.exe file. Note that yous sould use forward slash (/) or paired backslash (\\) instead of unmarried backslash (\).

   

   Now y'all can already access the repository using the following URL schema: "svn+ssh://username@hostname/path/to/repository". But the plug-in makes many connections to repository, and you will be prompted for a password every time a new connection requested. This is considering all hallmark is performed by SSH itself, therefore Subversion password caching feature does not work. Then the next footstep is to ready up a fundamental hallmark for SSH.
4. Generate a new SSH-2 RSA individual/public central pair or convert your existing private key to PuTTY format using PuTTYgen utility.

   

5. Put your public cardinal on the server. If it doesn't already exist, create the authorized_keys file (on Unix, typically ~/.ssh/authorized_keys). Each line in this file describes a public fundamental that is allowed to connect. Identify your public key hither.
6. Open up PuTTY. Enter hostname or IP address of the server.

   

7. Under "Connection" / "Information" enter the user name in the "Auto-login username" field.

   

8. Under "Connection" / "SSH" / "Auth" click on "Browse..." and indicate on your private primal file.

   

9. Go back to the "Session" category. Enter the session proper name and click "Salvage".

   

10. Open the session you have but created. It should not prompt you lot for username and countersign, because a fundamental authentication is used now. If you logged in successfully, this means that SSH configured correctly.
11. Now you tin connect to repository using the session proper noun instead of username@hostname, for example "svn+ssh://svnsrv/usr/svn". Open your IDE and work with your projects as usual. Note that the username provided by the IDE will be ignored.

    

Hints

Specifying the individual key file direct in the SVN_SSH variable

Y'all can use fundamental authentication without saving of a PuTTY session. Just specify a path to the private fundamental file as a parameter of TortoisePlink.exe in the SVN_SSH variable. For case,

fix SVN_SSH="C:/Program Files/TortoiseSVN/bin/TortoisePlink.exe" -i C:/ssh/id_rsa.ppk

With this configuration you should specify the user name and the host proper name (or IP accost) straight in the SVN URL, for example svn+ssh://user@192.168.0.i/var/svn. Culling way is to specify the user proper name as an boosted parameter for TortoisePlink:

set SVN_SSH="C:/Program Files/TortoiseSVN/bin/TortoisePlink.exe" -i C:/ssh/id_rsa.ppk -50 username

Using the configuration file instead of the environs variable

You can use Subversion configuration file instead of the SVN_SSH environs variable. Usually it is located in user'south folder, for example "C:\Documents and Settings\UserName\Awarding Data\Subversion\config ". The file already contains the description of available parameters. Place your SSH configuration in the [tunnels] section of the file. For example,

[tunnels] ssh = $SVN_SSH "C:/Program Files/TortoiseSVN/bin/TortoisePlink.exe" -i C:/ssh/id_rsa.ppk

Using other SSH clients

You tin apply plink.exe from PuTTY or ssh.exe from OpenSSH instead of TortoisePlink.exe. The principal disadvantage of this utilities is that console window appears when the utility started. TortoisePlink is a modified version of PuTTY plink, that uses graphical windows instead of a text console. Information technology shares configuration settings with PuTTY. If you wish to use OpenSSH client as a tunneling tool, you should prepare fundamental authentication for information technology in a different style, not as described above. The detailed description of this process included in the OpenSSH distribution (refer to the "Key Based Hallmark" document).

plink hangs nether VMware with Windows 2000 installed

While testing our software nether VMware with Windows 2000 installed we have noticed that plink.exe sometimes hangs after a TCP/IP connexion with a server was established, only before logging in. It also applies to TortoisePlink.exe. At the same time under Windows XP the aforementioned version of plink.exe works perfectly with the same server. If you lot have encountered such a problem, endeavor to apply bridged network connectedness instead of NAT connection for your virtual automobile.

---

linniumber55.blogspot.com

Source: http://www.pushok.com/help/svnscc/adv/svnssh.html

Share this post