For SmartGit, our graphical Git client, the 2nd release-candidate for the upcoming version 1.5 is available for download.
We released a bug fix for SmartCVS 7.1. It only contains bug-fixes and we recommend to update for anyone.
For svnserve, SASL is configured in the sasl section of conf/svnserve.conf, see below.
Depending on the Java Virtual Machine settings, high values for min-encryption may cause the authentication to fail. A solution is either to decrease this value or to upgrade the JVM to support the requested cipher strength.
Another cause for failures may be usage of too old JVMs. SASL authentication requires Java 1.5 or higher.
In /etc/sasl2 there are following files:
-rw-r--r-- 1 root root 49152 Apr 01 2009 sasldb_svn
-rw-rw-rw- 1 root root 135 Apr 01 2009 svn.conf
The /etc/sasl2/svn.conf is automatically read by svnserve (because it advertises itself as "svn").
Its list contains all possible mechanisms to use. When it comes to a handshake only those are used that satisfy svnserve.conf conditions (anonymous access support, encryption support, etc). Users and their passwords are validated against sasldb_svn database. A possible output of
# sasldblistusers2 /etc/sasl2/sasldb_svn
might look like:
Only alex has access to the repository with “svnkit.com” realm.
While installing msysgit, you will have the choice whether to launch the git commands using the Windows command prompt or the Git bash prompt. Be sure to select the Git bash prompt, because otherwise you will get the Git warning message “FIND: Parameter format not correct” executing Git commands.
Sometimes SVN servers are not directly accessible from the Internet, but hidden behind a corporate firewall. Using SSH tunnels is a way to allow access to such servers.
For such environments, the built-in SSH client of SmartSVN can’t be used as it requires direct access to the repository server. However, you can configure and use your system SSH to connect to such repositories.
The easiest way will be to use SSH’s ProxyCommand which can be configured in your .ssh/config file (details).
For my environment, I’m accessing our internal smartserver over the gateway gateway. So my configuration looks like:
ProxyCommand ssh gateway nc -w 1 smartserver 22
I have stripped off the passwords from both private key files, so authentication requires no interaction (refer here for details). That’s an important step to avoid the OpenSSH password prompt or — even worse — get stuck, if that GUI-prompt does not work. Now I’m able to connect to smartserver via the gateway, simply by invoking:
In SmartSVN’s Repository Profiles I have set up following tunnel:
In the Add Repository Profile wizard, I have entered URL svn+ssh://smartserver/repos/smartsvn and on the Details page, selected Tunnel set to ssh-gateway. That’s it!