On 2008-07-26 00:06, Ludek Finstrle wrote:
> Thu, Jul 24, 2008 at 12:25:36PM +0100, Matthew Richardson napsal(a):
> > I was following this thread with interest, and it seems to have dried up - can
> > anyone give me any more information on the status of MIT Kerberos within
> > TortoiseSVN or the neon libraries?
> I made no progress with Joe. I sent him the link to archive for this mail
> thread as he asked. I'm giving it up. Feel free to continue in this battle.
> I'm unable to create the dev environment for 1.4 and 1.5 due to lack of
> time and some problems I had. I'll try to finish the dev env and upload
> the patched TSVN somewhere. But don't hold your breath.
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.
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.
Alec.Kloss_at_oracle.com Oracle Middleware
PGP key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x432B9956
Received on 2008-07-26 05:01:48 CEST
- application/pgp-signature attachment: stored