Hi!

Yesterday I checked out from a svn repository using https as its transport. The problem is that it's a self signed certificate so curl complained about it and didn't let me do anything with the repo.

I was able to do the checkout with https+urllib but then the checkout branch is using https. I tried performing an update and it complained about the certificate.

I had to perform a pull specifying the repository address by hand (with https+urllib). I'm afraid that when I do the push from my local branch, it won't be reflected on the svn branch.

Is there a way to install the public key of the server so that curl won't complain or, perhaps, change the checkout branch so that it uses https+urllib?

Thanks in advance.

By the way, I tried appending the pem certificate from the server (exported from ff) to the /etc/ssl/certs/ca-certificates.crt file but still curl complained about the certificate.

I'm following instructions from http://turboflash.wordpress.com/2009...d-certificate/ and I just can't make curl to trust my certificate.

When I run the update-ca-certificates, it even names my certificate but still when I run the bzr update, I still get the curl complaining about the certificate. What do I have to do?

Is the certificate that apache uses on https the ca.crt that it uses to sign it? I guess not, right? Do I need to get the ca.crt used by apache to sign the certificate to add it to the trusted certificates?