Alec Kloss wrote:
> I've had some success using the GSSAPI support in SASL with
> Tortoise. It's got some nice perks compared to Negotiate auth...
> like not needing all the hassle of setting up certificates for SSL
> and the pesky performance problems with mod_dav_svn. And, best of
> all, since SASL dynamically loads auth modules, you just need to
> build it and drop it (along with the MIT libraries) into a
> TortoiseSVN bin/ directory and everything just works.
How big are those libraries of yours?
Do you have build instructions?
> Stefan, any thoughts about including the GSSAPI module in the SASL
> you build with Tortoise? I found that, if the MIT libraries aren't
> present, SASL quietly eats the load error and disables GSSAPI.
> Worst case, the SVN library reports that it can't negotiate
> authentication with the server... it's pretty slick. Or, you
> could probably bundle MIT Kerberos for Windows in Tortoise. As I
> read the license on their source code, you can do pretty much
> whatever you want with MIT Kerberos, except possible export it
> and use MITs name to advertise.
It depends on how big the libraries are. And if we can build them
without patching the sourcecode.
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
Received on 2008-07-28 16:58:31 CEST