git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ilari Liusvaara <ilari.liusvaara@elisanet.fi>
To: Junio C Hamano <gitster@pobox.com>
Cc: Konstantin Khomoutov <flatworm@users.sourceforge.net>,
	Sergey Sharybin <sergey.vfx@gmail.com>,
	Git List <git@vger.kernel.org>
Subject: Re: git:// protocol over SSL/TLS
Date: Sat, 28 Dec 2013 22:00:07 +0200	[thread overview]
Message-ID: <20131228200007.GA13655@LK-Perkele-VII> (raw)
In-Reply-To: <7viouaj5p0.fsf@alter.siamese.dyndns.org>

On Fri, Dec 27, 2013 at 02:21:31PM -0800, Junio C Hamano wrote:
> Konstantin Khomoutov <flatworm@users.sourceforge.net> writes:
> >
> > The Git protocol does not implement it itself but you can channel it
> > over a TLS tunnel (via stunnel for instance).  Unfortunately, this
> > means a specialized software and setup on both ends so if the question
> > was about a general client using stock Git then the answer is no, it's
> > impossible.
> 
> Hmph, I somehow had an impression that you wouldn't need anything
> more complex than a simple helper that uses git-remote-ext on the
> client side. On the remote end, you'd need to have something that
> terminates the incoming SSL/TLS and plugs it to your git daemon.

If you have some tool that can do cleartext I/O from stdin/stdout
and establishes ciphertext connection itself, you can use it with
git-remote-ext. It was written for cases exactly like that.

To do git:// inside, use the %G pseudo-argument.

-Ilari

      reply	other threads:[~2013-12-28 20:09 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-27 12:59 git:// protocol over SSL/TLS Sergey Sharybin
2013-12-27 13:29 ` Andreas Schwab
2013-12-27 13:36 ` Konstantin Khomoutov
2013-12-27 13:58   ` Sergey Sharybin
2013-12-27 14:12     ` Andreas Schwab
2013-12-27 14:16       ` Konstantin Khomoutov
2013-12-27 14:18       ` Sergey Sharybin
2013-12-27 14:20       ` Matthieu Moy
2013-12-27 14:25         ` Sergey Sharybin
2013-12-27 14:39           ` Konstantin Khomoutov
2013-12-27 14:47             ` Sergey Sharybin
2013-12-27 14:56               ` Konstantin Khomoutov
2013-12-28  9:37               ` Jeff King
2013-12-27 16:26           ` Bernhard R. Link
2013-12-28 20:52             ` Sergey Sharybin
2013-12-28  0:11           ` brian m. carlson
2013-12-27 14:29         ` Andreas Schwab
2013-12-27 14:21       ` Pyeron, Jason J CTR (US)
2013-12-27 14:14     ` Konstantin Khomoutov
2013-12-27 22:21   ` Junio C Hamano
2013-12-28 20:00     ` Ilari Liusvaara [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=20131228200007.GA13655@LK-Perkele-VII \
    --to=ilari.liusvaara@elisanet.fi \
    --cc=flatworm@users.sourceforge.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=sergey.vfx@gmail.com \
    /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).