From: Alex Riesen <raa.lkml@gmail.com>
To: Josef Wolf <jw@raven.inka.de>
Cc: git@vger.kernel.org
Subject: Re: How to push to http(s) repository with authentication?
Date: Thu, 23 Oct 2008 21:05:44 +0200 [thread overview]
Message-ID: <20081023190544.GA21079@blimp.localdomain> (raw)
In-Reply-To: <20081023175336.GA3526@raven.wolf.lan>
Josef Wolf, Thu, Oct 23, 2008 19:53:37 +0200:
> On Mon, Oct 20, 2008 at 08:25:02PM +0200, Josef Wolf wrote:
>
> > I have set up a repository as described in
> >
> > http://www.kernel.org/pub/software/scm/git/docs/howto/setup-git-server-over-http.txt
> >
> > over SSL with basic authentication. DAV access works fine with konqueror,
> > cadaver and and curl, using this .curlrc:
> > [ ... ]
>
> Is nobody interested in this topic? Or am I in the wrong list?
--cacert <CA certificate>
(SSL) Tells curl to use the specified certificate file to verify
the peer. The file may contain multiple CA certificates. The
certificate(s) must be in PEM format.
curl recognizes the environment variable named ’CURL_CA_BUNDLE’
if that is set, and uses the given path as a path to a CA cert
bundle. This option overrides that variable.
The windows version of curl will automatically look for a CA
certs file named ´curl-ca-bundle.crt´, either in the same direc‐
tory as curl.exe, or in the Current Working Directory, or in any
folder along your PATH.
If curl is built against the NSS SSL library then this option
tells curl the nickname of the CA certificate to use within the
NSS database defined by the environment variable SSL_DIR (or by
default /etc/pki/nssdb). If the NSS PEM PKCS#11 module (lib‐
nsspem.so) is available then PEM files may be loaded.
If this option is used several times, the last one will be used.
Does this (setting $CURL_CA_BUNDLE) help?
next prev parent reply other threads:[~2008-10-23 19:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-20 18:25 How to push to http(s) repository with authentication? Josef Wolf
2008-10-23 17:53 ` Josef Wolf
2008-10-23 19:05 ` Alex Riesen [this message]
2008-10-23 22:32 ` Josef Wolf
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=20081023190544.GA21079@blimp.localdomain \
--to=raa.lkml@gmail.com \
--cc=git@vger.kernel.org \
--cc=jw@raven.inka.de \
/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).