git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josef Wolf <jw@raven.inka.de>
To: git@vger.kernel.org
Subject: Re: How to push to http(s) repository with authentication?
Date: Fri, 24 Oct 2008 00:32:56 +0200	[thread overview]
Message-ID: <20081023223256.GB3526@raven.wolf.lan> (raw)
In-Reply-To: <20081023190544.GA21079@blimp.localdomain>

On Thu, Oct 23, 2008 at 09:05:44PM +0200, Alex Riesen wrote:

Thanks for your response, Alex!

[ ... ]
>        --cacert <CA certificate>
[ ... ]

> Does this (setting $CURL_CA_BUNDLE) help?

Well, as I wrote in my original mail, I already got the certificate
working.  My problem is the usage of the .netrc file.  I don't want
to store passwords in cleartext in files.

So the real question is: how do I make git-http to ask for credentials.

Sorry, I should have made more clearly what's the problem.

      reply	other threads:[~2008-10-23 22:41 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
2008-10-23 22:32     ` Josef Wolf [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=20081023223256.GB3526@raven.wolf.lan \
    --to=jw@raven.inka.de \
    --cc=git@vger.kernel.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).