Community
Participate
Working Groups
Hi there, I cannot commit to the DSDP TM / TCF SVN Repo here: svn+ssh://dev.eclipse.org/svnroot/dsdp/org.eclipse.tm.tcf/trunk Read-access works fine, but when trying to commit, it gets stuck near the end. It says that data is being transferred, but the the operation is just stuck. I have tried TortoiseSVN (Windows), Subclipse+JavaHL (Windows), Subversive+JavaHL (Windows), Subclipse+SVNKit (Linux). All with no luck. I am very certain that I (as the project lead) should have write access to the SVN repo. What can be broken here? FYI I'm located in Salzburg, Austria (In case network latency plays a role here). CVS, Wiki, build.e.o SSH shell, Hudson etc access all work fine.
I think that this may be related to the 16 group limit on NFS. Here's a question: can you commit using https? -M.
Ping? I really need to do some work on SVN...
How do I "commit using https" ?
I can certainly commit to the TM CVS, if that helps.
(In reply to comment #3) > How do I "commit using https" ? Replace svn+ssh with https.
Matt and I have looked at the repo itself and cannot see anything wrong. If you can test commits over https that would be great.
In fact https:// access works fine. I was not aware that https is available. Is svn+ssh deprecated? I remember that in the old days, only svn+ssh was available.
It's not deprecated. In fact, we much prefer committers use ssh+svn since it's more secure. But this repo was already "https-enabled" and you needed a workaround. We'll have to investigate to find the cause of the problem.
Hm... I'm surprised that https: is considered less secure. Given that lots of banking apps also use https... Anyways, here's a hunch regarding the svn+ssh problem: I have always only driven this from UI tools (Subclipse, Subversive, TortoiseSVN) and never from commandline. Just in case some interactive question comes in over the ssh tunnel for any reason, that would probably explain why the commit cannot continue but hangs. Strange thing is though, I can perform all read operations... it only hangs when I try to commit. Unfortunately I have no idea how to better diagnose this on my end. I'm reopening the bug for the svn+ssh specific case, but with lower severity since I now have a workaround. Many thanks!
> Hm... I'm surprised that https: is considered less secure. Given that lots of > banking apps also use https... Because banking over a VPN tunnel is not practical for the common user :-) It's less secure in the sense that, regardless of whether or not you are logged in, the web server user account has write access to your repository. Theoretically, if an exploit is found in an Apache module, or even in a related software like IPZilla for instance, then that could be used to compromise your repository. SSH drops privilege to your user id as soon as authentication is complete, so any exploits would limit damage to what you have write access to. Thanks for reopening -- we'll have to see what is causing this.
Martin, are you still experiencing this? Or have you moved your repos to Git?
I personally don't use any svn repos any more - the https method was a good workaround.
Let's call it fixed :)
Movng to Subversion component.
