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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Jan 13, 2010 at 3:06 PM, Ilari Liusvaara
<ilari.liusvaara@xxxxxxxxxxx> 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.

>> 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
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]