Re: should we really ship serf as default for 1.7?
Stefan Küng <tortoisesvn_at_gmail.com> wrote on 06/24/2011 09:04:41 AM:
> On 24.06.2011 15:50, Mark Phippard wrote:
> > On Fri, Jun 24, 2011 at 9:48 AM,<kmradke_at_rockwellcollins.com> wrote:
> >> Is anybody using serf with negotiate authentication? I can't get it
> >> work with a 1.6.5 server using mod_auth_kerb and negotiate.
> >> The server sends the 401:
> >> WWW-Authenticate: Negotiate
> >> WWW-Authenticate: Basic realm="my realm"
> >> correctly, but serf just keeps re-sending the same original
> >> unauthenticated
> >> request. Works fine if negotiate is removed, and works fine either
> >> when switched to use neon.
> >> I tested with the collabnet 1.7.0-dev build r1136035. User agent
> >> SVN/1.7.0-dev serf/0.8.0
> > I am not building with Kerberos. Wouldn't I need to compile with that
> > for the support to be included? I would try the TortoiseSVN nightlies
> > as I think Stefan includes GSSAPI in his builds.
> Yes, TSVN is built with Kerberos support. But it's shipped without any
> kerberos dlls - users have to install those separately.
> To avoid linker problems, we have our own gssapi header and cpp file
> which we link against, and that then loads the installed dlls
> dynamically if they're available. Here are our files in case someone
> else want's to link their client with those:
Since neon "just works" for negotiate authentication without any
user configuration, I think that alone would be enough for any larger
company to want to keep neon as the default library...
Received on 2011-06-24 16:22:53 CEST
This is an archived mail posted to the Subversion Dev