From: Edward Ned Harvey <git@nedharvey.com>
To: "'Shawn Pearce'" <spearce@spearce.org>
Cc: <git@vger.kernel.org>
Subject: RE: git and SSL certificates
Date: Fri, 24 Feb 2012 15:01:42 -0500 [thread overview]
Message-ID: <000801ccf32f$2448e030$6cdaa090$@nedharvey.com> (raw)
In-Reply-To: <CAJo=hJuyHv_L_zajW-MWEj6fDGggrVDkRWT32mD5TBzD_GzReQ@mail.gmail.com>
> From: Shawn Pearce [mailto:spearce@spearce.org]
> Sent: Friday, February 24, 2012 2:27 PM
>
> Nope. Git uses the system's libcurl, which is probably using the
> system's libssl or libgnutls, which is using the system's
> certificates.
Thanks, this gives me more fuel to go on, because now I know I can reproduce
the problem using any other tool I want - curl for example. Where I'm able
to specify -v for verbose, and get its cert search path.
It's still really bizarre, because the Startcom root CA is indeed present in
the search path, and it is indeed the same root CA that was used to sign my
server cert. So now I'll go ask startcom what they think about it...
If anyone is interested, please say so, and I'll report back here.
Otherwise, I'll probably just let the thread die.
prev parent reply other threads:[~2012-02-24 20:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 19:11 git and SSL certificates Edward Ned Harvey
2012-02-24 19:27 ` Shawn Pearce
2012-02-24 20:01 ` Edward Ned Harvey [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000801ccf32f$2448e030$6cdaa090$@nedharvey.com' \
--to=git@nedharvey.com \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).