Re: git + davfs2, is it safe?

From: Shawn O. Pearce <spearce@spearce.org>
Date: Feb 9, 2010, 17:57 UTC
Message-ID: <20100209175712.GB28936@spearce.org>
In-Reply-To: <2c173a351002090839v45d01d5dt17e4b4af37e84615@mail.gmail.com>

G?bor Farkas <gabor@nekomancer.net> wrote:

Show 10 quoted lines

> for various reasons our git repositories are hosted using https (webdav),
> which is http-auth and client-certificate authenticated.
> 
> (linux on both the server and the client)
> 
> it's possible to somehow persuade git to push/fetch from such repositories,
> but it's very annoying because either you have to enter your
> username+password+cert_password
> on every fetch and twice on every push, or you have to write them down
> in $HOME/.netrc .

This is why I prefer SSH. You have ssh-agent around to retain your key for you.

A more modern Git (1.6.6 or later IIRC) should avoid prompting for the password twice, because the HTTP client should actually reuse the connection for the subsequent requests. But I haven't tested it.

You might also want to consider upgrading your server to post-1.6.6 and stop using WebDAV... but instead use smart HTTP for push. That should only need one authentication cycle to perform the push.

It sounds like its time for a proper curl-agent for libcurl though.
Users and applications shouldn't have to keep implementing their
password stores as text files...

-- 
Shawn.