On Jun 16, 2010, at 14:41, Will Shackleford wrote: > We have a lot of trouble with the fact that subversion needs to use multiple > ssh connections to do a > single svn update. Our firewall only allows one connection through before you > have to login to the firewall > again. (which is an incredible pain) > Also tortoisesvn doesn't seem to be integrated with an ssh-agent so the > windows users need to > type their username and password 3 times even when not going through the > firewall. > > Directly accessing the repository files or using the pserver are not really > options for us, given the > need to administer users and open up the network ports etc. > > Is there a way it can be reconfigured now to use only a single ssh connection > now or > should submit and issue for this to be fixed later?
Neither, probably. Subversion uses multiple ssh connections. I doubt this will change. But I'm just a user, not a developer. You should probably file a bug report with whoever configured your firewall to work that way, because it is not compatible with how Subversion uses ssh. You could also consider using http or https instead of ssh.
