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

Re: --non-interactive causing auth failure?

From: David Abrahams <dave_at_boostpro.com>
Date: Wed, 8 Apr 2009 19:59:03 +0000 (UTC)

David Abrahams <dave <at> boostpro.com> writes:

>
> I can "svn up" and it works fine without asking for any passwords, but
> when I "svn up --non-interactive", I get
>
> svn: OPTIONS of 'https://my-server/and/path': authorization failed:
> Could not authenticate to server: rejected Basic challenge
> (https://my-server)

It turns out that when I remove the auth cache and update again, Subversion
tells me that the server certificate isn't trusted:

Error validating server certificate for 'https://my-server:443':
 * The certificate is not issued by a trusted authority. Use the
   fingerprint to validate the certificate manually!
Certificate information:
 * Hostname: my-server
 * Valid: from Mon, 23 Jun 2008 00:00:00 GMT until Sat, 23 Jun 2012 23:59:59
 GMT
 * Issuer: Network Solutions L.L.C., US
 * Fingerprint: f5:3e:6a:3c:4c:dd:4b:18:6c:4b:4e:23:7d:db:38:10:89:32:f3:7d

This doesn't seem right. Network Solutions should be a trusted authority,
shouldn't it? I'm on MacOSX with MacPorts, FWIW.

--
Dave Abrahams
BoostPro Computing
http://boostpro.com
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1601401
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-04-08 22:00:13 CEST

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

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