On 21.03.2013 14:24, Keiran Sweet wrote:
> Hi Everyone,
> I've posted previously about having issues with getting krb5 + HTTPS functionality working reliably in the past [1] where all tortoise clients work OK for a period of time, then they suddenly stop. It seems now that the SASL/neon functionality was broken around the 1.6.16 mark [2] and never really fixed.
>
> I've come across a few posts lately that suggest moving to the serf libraries to get this working by adding the following lines to the tortoise configuration file's [global] section:
>
> http-library = serf
>
> However, when I do this on my platform (Windows XP and 7 , 32-Bit) it hangs indefinately, with the following errors in apache constantly repeated ( The server is a Apache + DAV + SVN + HTTPS + KRB5 platform : )
>
> 10.2.3.4 - - [19/Mar/2013:16:27:46 +0000] "OPTIONS /svn/reponame HTTP/1.1" 401 498
>
> 401 = Unauthorized. Using other clients with the same credentials works fine, so this is specifically a Tortoise SVN issue.
Other clients: also other Windows clients that use the official svn library?
> Would I be able to get an official status on krb5/sasl/neon/serf/GSSAPI + HTTPS support for Tortoise 1.7 ?
>
> Specifically:
> * Is this a supported configuration for Tortoise ?
> * Is there any known bugs/issues with this configuration that prevent it from working ?
> * Is there any way to debug neon/serf issues further from the client side ?
> * Is there the possibility for us to fund (within reason) the fix of this issue if it isnt a priorty ?
>
> I ask this as I'm really keen to move our users from a messy svn+ssh configuration to a clean KRB5/HTTPS environment as the management overhead is pretty ugly on the server side.
* neon is gone in svn 1.8, there's only serf left (not released yet, but
you can try a nightly build).
* Serf is now at version 1.2.0, maybe your issues are fixed now? You can
try a nightly build if you like.
* you didn't mention the TSVN version you're using for your tests
* if you have issues with GSSAPI and authentication, always first try
the official svn command line client. If the issue is there too, you
have to report your problems to the svn users list. Because if the issue
is there too, it's in the svn library and therefore needs to be fixed there.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest interface to (Sub)version control
/_/ \_\ http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=3051657
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-03-21 21:42:12 CET