On Fri, Jun 24, 2011 at 9:51 AM, Benjamin Podszun < [email protected]> 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. > Thanks for the feedback! In fact, one of the things I didn't mention about SSH vs HTTPS is actually security. The fact that users connecting over SSH need a system account on the server is something I'd love not to have to worry about. The ability to restrict which command a user is allowed to run helps a lot, and the gitorious script is really restrictive, but still I'd prefer not having one. On the gitorious.org servers, the public facing IP address and port run as an unprivileged user (git), but most local installations probably use OpenSSH's defaults, leaving the SSH port open. 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 actual client certificate to gain access to someone else's account, not just a password which may be shared between different sites > So my vote, if I get any, is: > Please keep ssh support as a maintained and stable option. I don't > care if installation instructions focus on http in the future (so - go > ahead and promote http over ssh, make the http experience a lot easier > to set up or something), but please don't remove the ssh handler or > let it rot. > Got it. > Ben, running a gitorious installation with a couple dozen users for > 1.5 years now > :-) - Marius -- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected]
