git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Avery Pennarun <apenwarr@gmail.com>
To: Ilari Liusvaara <ilari.liusvaara@elisanet.fi>
Cc: Andreas Krey <a.krey@gmx.de>,
	Nguyen Thai Ngoc Duy <pclouds@gmail.com>,
	git@vger.kernel.org
Subject: Re: [RFC 0/2] Git-over-TLS (gits://) client side support
Date: Thu, 14 Jan 2010 15:46:56 -0500	[thread overview]
Message-ID: <32541b131001141246o1f5ce816gc4a26b81343aaa2d@mail.gmail.com> (raw)
In-Reply-To: <20100114085124.GA10298@Knoppix>

On Thu, Jan 14, 2010 at 3:51 AM, Ilari Liusvaara
<ilari.liusvaara@elisanet.fi> wrote:
> The client tries only one auth method instead of potentially trying
> multiple. Witness the 'use verbose mode and check if it uses the key'
> type stuff.

I believe this is a limitation of the client, not of the protocol.  So
a patch to the ssh client could fix this.

> OpenSSH? With the level of paranoia in it, I'd say good luck. And
> it's not just client, its the server also (and especially the
> server).

But you could fork it if you wanted.  It's about as easy to convince
me to install a different version of ssh than to install
yet-another-security-server.  (In fact, it might be easier to get me
to put in a patched openssh; at least then I can trust that it's
mostly openssh, and examine just what's different in your version.)

> And if you host the repo system too, you would get second key anyway
> (and SSH is not too good at handling multiple keys).

I'm not really sure about this.  ssh-add seems pretty easy.

Have fun,

Avery

  reply	other threads:[~2010-01-14 20:48 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-13 13:19 [RFC 0/2] Git-over-TLS (gits://) client side support Ilari Liusvaara
2010-01-13 13:19 ` [RFC 1/2] Git-over-TLS (gits://) client side support (part 1 of 2) Ilari Liusvaara
2010-01-13 13:19 ` [RFC 2/2] Git-over-TLS (gits://) client side support (part 2 " Ilari Liusvaara
2010-01-13 13:25   ` Alex Riesen
2010-01-13 13:39 ` [RFC 0/2] Git-over-TLS (gits://) client side support Nguyen Thai Ngoc Duy
2010-01-13 13:57   ` Ilari Liusvaara
2010-01-13 14:12     ` Andreas Krey
2010-01-13 14:47       ` Ilari Liusvaara
2010-01-13 16:17         ` Andreas Krey
2010-01-13 17:36           ` Ilari Liusvaara
2010-01-13 18:35             ` Andreas Krey
2010-01-13 19:18               ` Ilari Liusvaara
2010-01-13 19:30                 ` Avery Pennarun
2010-01-13 20:06                   ` Ilari Liusvaara
2010-01-13 20:13                     ` Avery Pennarun
2010-01-13 21:04                       ` Ilari Liusvaara
2010-01-13 22:03                         ` Avery Pennarun
2010-01-13 22:06                           ` Shawn O. Pearce
2010-01-13 23:00                           ` Ilari Liusvaara
2010-01-13 23:51                             ` Avery Pennarun
2010-01-14  8:51                               ` Ilari Liusvaara
2010-01-14 20:46                                 ` Avery Pennarun [this message]
2010-01-14 23:08                                   ` Ilari Liusvaara
2010-01-13 19:40                 ` Andreas Krey
2010-01-13 20:47                   ` Ilari Liusvaara
2010-01-13 19:11     ` Avery Pennarun
2010-01-13 20:00       ` Ilari Liusvaara
2010-01-13 20:13 ` Edward Z. Yang

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=32541b131001141246o1f5ce816gc4a26b81343aaa2d@mail.gmail.com \
    --to=apenwarr@gmail.com \
    --cc=a.krey@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=ilari.liusvaara@elisanet.fi \
    --cc=pclouds@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).