[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: svn+ssh :(

From: Kevin Wilson <Kevin.Wilson_at_comtrol.com>
Date: 2006-02-11 00:10:59 CET

---- This is real basic but it in a nutshell ----

setup your user accounts on the linux server.

enable password-less ssh connections and copy back a key to convert using
puttygen on your windows box:
http://www.novell.com/coolsolutions/feature/15314.html

In the ~/.ssh/authorized_keys file insert the following before the text
therein:

command="/usr/bin/svnserv -R /<your repo> -t --tunnell-user=<user>"

Now tell tsvn to use TortoisePlink.exe instead of Plink or Putty in the SSH
client setting.

Now follow the latter parts of the TSVN ssh howto to access the repo without
being prompted for a password.

cheers

-----Original Message-----
From: James Carr [mailto:james.r.carr@gmail.com]
Sent: Friday, February 10, 2006 14:56
To: users@tortoisesvn.tigris.org
Subject: Re: svn+ssh :(

I'd be interested in knowing...

On 2/10/06, Kevin Wilson <Kevin.Wilson@comtrol.com> wrote:
> This can be done without the use of pageant. Let me know if you want to
try
> my method.
>
> The biggest draw back is you cannot make SSH run a custom script to ensure
> the umask gets set to 002 and the SSH process is run under the svn owner
> account. It takes some careful setting of users/dir permissions but you
can
> get multi-user rw successfully.
>
> -----Original Message-----
> From: Alf Christophersen [mailto:alf.christophersen@medisin.uio.no]
> Sent: Friday, February 10, 2006 11:16
> To: users@tortoisesvn.tigris.org
> Subject: Re: svn+ssh :(
>
>
> At 17:05 10.02.2006, James Carr wrote:
> >Hi,
> >
> >I am having a small problemgetting svn+ssh to work nicely with
> >tortiseSVN. Every single action requires a prompt for password, even
> >when browsing one will be prompted for a password each time thy view a
> >directory through the repos browser.
> >
> >I found some tutorials on setting up ssh public key authentication,
> >but so far nothing seems to work. :(
>
>
> Download Putty and install that one. It contains a key generator and
upload
> the public key as described. Have Pageant start each time you log in, and
> in the cvs setup, tell plink be executed
>
> Now make a login profile in putty which you name after your username and
> server, like dude@nowhere.com if username is dude and server is
nowhere.com
>
> Start once plink with "plink dude@nowhere.com" if that was your profile
> name and then, eacjh time you login, activate pageant and read in the
> private key which you have stored somewhere. Then you may try plink again
> and check you get in directly on the server. Exit and use svn freely. But
> remember to reactivate key in Pageant each time you log in. If you in gthe
> startup starts a batch file that run through all directories that are
under
> svn and do an update, also have before that, a reminder to enter the
> password for svn login.
>
> Like
> Echo Please remember to log in at PageAnt
> cd project1
> svn update
> cd project2
> svn update
>
> etc etc
>
>
> Alf Christophersen
> http://folk.uio.no/achristo
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
> For additional commands, e-mail: users-help@tortoisesvn.tigris.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
> For additional commands, e-mail: users-help@tortoisesvn.tigris.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Sat Feb 11 00:12:43 2006

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.