maemo.org Bugzilla – Bug 4953
git fails to verify server SSL certificate due to missing root certificates
Last modified: 2010-04-16 02:06:05 UTC
You need to
before you can comment on or make changes to this bug.
(Copying from bug 4943 as that turned out to be a different issue)
Fremantle 5.0 beta 2 SDK.
STEPS TO REPRODUCE THE PROBLEM:
1. git clone https://git.maemo.org/projects/modest (or any other project)
Successful repository checkout.
[sbox-FREMANTLE_X86: ~] > git clone https://git.maemo.org/projects/modest
Initialized empty Git repository in /home/user/modest/.git/
error: error setting certificate verify locations:
warning: remote HEAD refers to nonexistent ref, unable to checkout.
EXTRA SOFTWARE INSTALLED:
ln -s /scratchbox/devkits/git/share/curl/curl-ca-bundle.crt /usr/share/curl/
Don't think that Janne is the best assignee here...
@Tero, do you have an idea who could handle this?
(In reply to comment #1)
> Don't think that Janne is the best assignee here...
> @Tero, do you have an idea who could handle this?
Yes, let me make a few inquiries down the corridor here and I'll add someone to
You're using git devkit, at least the workaround would suggest that the git
devkit is at least installed. Could you provide me your target configuration
data just to make sure, ie. do  in your current target.
Added myself as cc.
 sb-conf sh
(Changing summary, it's git (the tool) that fails, not git.maemo.org the
(In reply to comment #3)
> You're using git devkit, at least the workaround would suggest that the git
> devkit is at least installed. Could you provide me your target configuration
> data just to make sure
[sbox-FREMANTLE_X86: ~] > sb-conf sh
Devkits: perl debian-etch doctools svn git
Is there some other git I should be using? At least apt-cache doesn't show
It looks like the reason is that the certificate has expired. If you load
https://git.maemo.org/ in Firefox, you get:
"git.maemo.org uses an invalid security certificate.
The certificate expired on 16/12/09 00:59.
(Error code: sec_error_expired_certificate)"
(In reply to comment #5)
> It looks like the reason is that the certificate has expired.
It is, but that's of course a different issue than this. Sorry for the noise.
(I have opened bug 7136 about the expiry issue).
*** Bug 9935 has been marked as a duplicate of this bug. ***