[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: "Authorization failed" with windows server and solaris client

From: Florin Iucha <florin_at_iucha.net>
Date: 2002-09-30 19:52:26 CEST

On Tue, Sep 24, 2002 at 11:10:10AM -0500, Florin Iucha wrote:
> Hello,
> I have sucessfully installed a Subversion servers using Apache 2.0.42
> prerelease install and Subversion-r3200 on windows. I have configured
> the subversion repository to use basic authentication. I have compiled
> the client on Solaris using the r3200 source tarball.
> I can checkin/checkout fine using a windows client (svn.exe from the
> r3200 zip file) but when I attempt to do a checkout from Solaris using the
> same URL, it fails with:
> > svn co http://ahost__:8080/svn/scripts work
> fiucha's password:
> username: fiucha
> fiucha's password:
> svn: Authorization failed
> svn: PROPFIND of /svn/scripts: authorization failed

I have compiled subversion in maintainer mode, enabled neon logging to
stderr and then manually generated the base64 encoded password and
compared its length to the number of xxxes in the dumped header. Lo and
behold, the Authorization header generated by neon contained 4 xes less
than the one I manually generated.

Sure enough, changing my password to one 5 chars long (the initial one
has 9 characheres) made subversion happy.

So neon needs its base64 encoding fixed.


"If it's not broken, let's fix it till it is."
41A9 2BDE 8E11 F1C5 87A6  03EE 34B3 E075 3B90 DFE4

  • application/pgp-signature attachment: stored
Received on Mon Sep 30 19:53:13 2002

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.