[aur-general] Git over HTTPS

Alan Jenkins alan.james.jenkins at gmail.com
Tue Jun 16 06:24:05 UTC 2015

I am with the OP on this, having worked in a cloud security company I
understand why they block port 22 out bound and know it to be a common
problem. It is blocked to stop employees accidentally or intentionally
leaking important customer or business data. You can also use SSH to bypass
security measures in place within the network and even create tunnels back
into the network.

Seriously I believe that there should be the option to do git over ssh as
the limitation to just SSH is going to cause problems for those in
corporate environments meaning we will lose out.

On Tue, 16 Jun 2015 05:33 Eli Schwartz <eschwartz93 at gmail.com> wrote:

> It is not necessarily Arch's problem that a tiny minority of users have the
> standard connection methods blocked. While it would be nice if lots of
> options are offered for every possible scenario, that may not necessarily
> happen.
> Think of Github's alternative method as being a bonus, not something to be
> taken for granted. :)
> And the move to git repos may already be alienating some people.
> Regardless, progress and efficiency have been made a priority over
> preserving every last contributor.
> -- Eli Schwartz

More information about the aur-general mailing list