I wanted to jump into this dicussion to confirm the issue.
On Oct 23, 2007, at 8:38 PM, Jack Repenning wrote:
> On Oct 23, 2007, at 8:24 PM, patrick decaix wrote:
> > did you get an answer?
> > i have the same problem.
> One thing that can cause this is if your web server's SSL certificate
> is not properly signed, or expired, or something like that. [...]
This actually generates an error that mentions the certificate.
So, at the moment:
- I attempted a https://host/repos checkout, that failed with something
about the certificate.
- So, in the terminal I ran: svn ls https://host/repos,
and accepted the self-signed cert permantently.
- I tried again a checkout with SCPlugin. This time I got a PROPFIND
[...] authentication failed error, while I know I have access
with the specified username and password.
- When attempted on the terminal, I _can_ check out with:
svn co https://host/repos --username foo
In the terminal I can of course enter the password and SVN will remember
it, so SCPlugin will probably work for checkouts from this host. But,
when using another host the same problem will reappear. Somehow the
username and/or specified in SCPlugin's checkout dialog do not propagate
to the actual checkout command? Unfortunately I do not have logs of the
webserver, to see as who/how it tries to check out the repo to help you
P.S. Please Cc me, for I am not on the list.
PhD Student @ Eindhoven | email: paul@... University of Technology, The Netherlands | JID: paul@... >>> Using the Power of Debian GNU/Linux <<< | GnuPG key ID: 0x50064181