Subversion access over https

marsanyi

Sean, you note that I can set up an svn server and access over svn+ssh. I did that, works well. But: for Windows client (staging, production machines in the cloud) no ssh is available by default. What's the status of https: access for an OpalStack-hosted svn server?

sean

marsanyi Still on the TODO list, hopefully before the Dec 9 cutoff but we can't guarantee it.

What Windows svn client are you using?

marsanyi

Tortoise for GUI, command-line (my normal mode). More reading led me to setting SVN_SSH environment variable (https://stackoverflow.com/questions/16214136/how-to-use-svnssh-with-tortoise-svn-from-the-command-line) which seems to work. Now spelunking around trying to work out certificates, etc so I don't have to share passwords with the cloud machine. Ugh.

marsanyi

So, successfully limping along with a workaround for now. Don't rush to get the https: implementation just for me 🙂

sean

Glad you found an interim solution, thanks for sharing it 🙂

marsanyi

For other users, here's the summary, for clients on Windows using TortoiseSVN (gui-based client) and/or SlikSVN (command-line client):

to use SSH with public/private keys, first, set up PuTTY as per https://devops.ionos.com/tutorials/use-ssh-keys-with-putty-on-windows/ and follow the instructions under "Create new Public and Private keys". TortoiseSVN uses PuTTY's certificate handling by default. Install your client machine's public key on your Opalstacked machine's "authorized_keys" file as described. Try opening the connection, and verify that you can ssh into OpalStacked. Save the session configuration with a name, as described.
establish the TortoiseSVN connection by referring to the session configuration name in the connection string, as described at https://tortoisesvn.net/ssh_howto_logemann.html in the section "Testing SSH with TortoiseSVN". You can test using the "Repo-browser" menu item in Tortoise's context menu when clicked on a non-repo directory, oddly enough; it'll query for the URL you wish to use. If that works, use TortoiseSVN's "Relocate" context menu option to replace your existing workspace's source with the "ssh+svn" version.
tell SlikSVN to use Tortoise's ssh tunnel rather than its own, by changing the "ssh = " line (usually commented out) in SlikSVN's config file to point to TortoiseSVN's "TortoisePlink.exe" (in the /bin directory where you have Tortoise installed), as described in step 4. of http://www8.pair.com/dmurdoch/svnuser.html. Now SlikSVN will use Tortoise, which will use PuTTY, which will find and use your certificates.
Phew! Thanks, Google!

csd

Sean - we also require SVN over https. The SVN_SSH works well but the protocol is blocked from a few client locations.