Re: [RFC 0/2] Git-over-TLS (gits://) client side support

From: Avery Pennarun <apenwarr@gmail.com>
Date: Jan 13, 2010, 20:13 UTC
Message-ID: <32541b131001131213m75b4baefsc70a4cbf3c8431c8@mail.gmail.com>
In-Reply-To: <20100113200629.GA8383@Knoppix>

On Wed, Jan 13, 2010 at 3:06 PM, Ilari Liusvaara <ilari.liusvaara@elisanet.fi> wrote:

> On Wed, Jan 13, 2010 at 02:30:20PM -0500, Avery Pennarun wrote:
>> That's why every major web browser supports them. [X.509 client-side certificates]
>
> Supports != is actually usable.

Lots of people use it. That was my point. If it weren't important, web browser makers wouldn't bother putting it in; God knows they leave out a lot of other stuff that I'd like.

Show 5 quoted lines

>> Furthermore, how many people who really want ssh-style keypairs (and
>> thus refuse to use X.509 and PKI) can't just use ssh as their git
>> transport?  I don't actually understand what the goal is here.
>
> As said, I got fed up with failure modes of SSH.

I think this is the answer that needs clarification. What failure modes are these? ssh doesn't seem to fail for me. And github.com seems to be working rather well with a huge number of users and ssh authentication.

If you're upset at the failure modes of ssh, is it possible to fix ssh instead of introducing Yet Another Tunneling Protocol?

Have fun,

Avery