Your message dated Fri, 17 Oct 2008 10:47:58 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: libneon27-gnutls: latest upgrades broke svn https auth
has caused the Debian Bug report #498351,
regarding libneon27-gnutls: latest upgrades broke svn https auth
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
498351: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=498351
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: libneon27-gnutls
Version: 0.28.2-5
Severity: important
Hi,
I just got back from holidays, sync'ed our internal mirror, and done an
upgrade. When upgrading libneon27, it broke auth to our internal svn server,
using https.
It was working perfectly fine with -3, now with -5 svn keeps asking
username/password.
Adding --verbose to svn doesn't help. I'll try to see if I can debug with neon
directly, but I'm not sure how to do that.
Cheers,
--
Yves-Alexis Perez
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.24-etchnhalf.1-amd64
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
--- End Message ---
--- Begin Message ---
On Fri, Oct 17, 2008 at 09:22:13AM +0100, Joe Orton wrote:
> The problem is the domain parameter which the server is sending; it's
> invalid and excludes the /svn repository which you're trying to use, so
> neon refuses to use Digest auth for that path. "svnserver.tld/wsvn/"
> does not mean what you might expect, either, it would resolve to a URI
> of e.g http://blah/svnserver.tld/wsvn/, not http://svnserver.tld/wsvn/
>
> (The domain parameter is controlled by the AuthDigestDomain directive in
> the server config)
Thanks. That completely fix the problem. Indeed we had a <Location />
which was pointing to websvn, with a different AuthDigestDomain
directive.
>
> I might have to change neon to ignore the domain parameter in the case
> where it excludes the current request-URI, since that seems to be
> clearly a config error.
Thanks so much, it was really blocking for us, and not to easy to see
the problem (especially since it worked in previous versions :) ).
I'm closing the bug for now.
Cheers,
--
Yves-Alexis
--- End Message ---
