Hi,
I am pretty new to this list. Just joined yesterday, and only just getting a
gitorious installation setup behind the firewall. However, my thoughts are
if HTTP can offer everything that SSH can with the same reliability, rather
go with a single protocol. It would make the code easier to
On Fri, Jun 24, 2011 at 9:51 AM, Benjamin Podszun
benjamin.pods...@gmail.com wrote:
I would. The deployment of ssh is well-known and understood, and
probably already exists as a way to access machines/services in a lot
of shops. I trust ssh, trust the code quality and security audits.
Hello,
We'll investigate what it will take to use SSL client certificates for
authentication, since this will:
- save the users from entering their passwords when pushing/putting the
credentials in .git/config or elsewhere
- provide better integrity for credentials: you'd need access to the
I have a concern with the practicality of using client certificates
over https instead of SSH.
You can tell git which key and cert to use for client cert https
connections. This is done via git-config, so it can be set both
globally (--global, stored in ~/.gitconfig) and per project (/path/to/
Well I'm quite faint hearted and I have installed Gitorious a number of
times (4-5) so I don't really think it is that hard...
Please keep the SSH and Git protocols as they are. People like me expect
it to work the same way at Gitorious as it does according to the Git
documentation.
For my own
Another open question: Do clients actually support this http based
cloning decently? Think Git Extensions, TortoiseGit et al?
--
To post to this group, send email to gitorious@googlegroups.com
To unsubscribe from this group, send email to
gitorious+unsubscr...@googlegroups.com
Hi Marius,
First, I would like you to congratulate you and Johan for the good work
and efforts you both put on this feature.
Then, I would like to say that I would be really really sad if SSH
support was deprecated. I think that providing your public key from a
user's point of view is
Hi Marius,
I don't think it is a good idea to drop/deprecate support for ssh or
git-proxy. But I do like the approach of having modularized protocols, maybe
ssh and git handler should be refactored to its own modules? So one can
choose what it wants to install.
Any way, great job!
Cheers
On
On Fri, Jun 24, 2011 at 11:51, August Lilleaas augustlille...@gmail.comwrote:
I have a concern with the practicality of using client certificates
over https instead of SSH.
You can tell git which key and cert to use for client cert https
connections. This is done via git-config, so it can be
First, I would like you to congratulate you and Johan for the good work and
efforts you both put on this feature.
Thanks, but my name is Christian. Johan stepped down, remember? :)
Then, I would like to say that I would be really really sad if SSH support
was deprecated. I think that
So - although I still think that ssh should stay and that GUI client
support is a valid point: I cannot ignore the thought that I might be
just a lazy bum that wants to keep it as it is, for the sake of it.
:) No worries. You are definitely right in that we want to reach a wider
audience, but
Thanks, but my name is Christian. Johan stepped down, remember? :)
Right, sorry, Christian. It is just the new age's effect :)
;)
If you could have well-performing, secure and easy-to-use HTTP pull/push,
then why wouldn't you use it?
Because I want all my repository submodules URL
12 matches
Mail list logo
