Re: [aur-general] Git over HTTPS
Asking for a response from the OP: Do you not have other network access available to maintain your AUR packages? More to the point, are you maintaining packages on AUR as part of your official responsibilities? Or just in spare time? Leaving aside, for the moment, all other arguments regarding blocking outbound SSH, I believe these are fundamental questions.
To answer your questions: 1. Yes, I do have network access outside of my corporate environment. However, much (READ: all) of the project maintenance and code lives on and is performed on my corporate servers. 2. I currently maintain the ownCloud-beta-client package as part of my involvement with that group. This is done as part of my official duties in my corporate environment. My organization is also looking to begin sharing several large projects within a few months. Without another form of access, this would be technically impossible. -- Thomas Swartz
On Wed, Jun 17, 2015 at 2:17 PM, Tom Swartz
To answer your questions:
1. Yes, I do have network access outside of my corporate environment. However, much (READ: all) of the project maintenance and code lives on and is performed on my corporate servers.
2. I currently maintain the ownCloud-beta-client package as part of my involvement with that group. This is done as part of my official duties in my corporate environment.
Aren't you moving what essentially would be your problem outside your firewall, too? cheers! mar77i
On 17-06-15 14:17, Tom Swartz wrote:
Asking for a response from the OP: Do you not have other network access available to maintain your AUR packages? More to the point, are you maintaining packages on AUR as part of your official responsibilities? Or just in spare time? Leaving aside, for the moment, all other arguments regarding blocking outbound SSH, I believe these are fundamental questions.
To answer your questions:
1. Yes, I do have network access outside of my corporate environment. However, much (READ: all) of the project maintenance and code lives on and is performed on my corporate servers.
2. I currently maintain the ownCloud-beta-client package as part of my involvement with that group. This is done as part of my official duties in my corporate environment.
My organization is also looking to begin sharing several large projects within a few months. Without another form of access, this would be technically impossible.
Tom, sofar many people have responded, but 1 name is missing : Lukas Fleischer, our valued aur web maintainer. I suggest you create a feature request for AUR git over https support at https://bugs.archlinux.org/index.php?project=2 . LVV
Em 17-06-2015 15:51, LoneVVolf escreveu:
sofar many people have responded, but 1 name is missing : Lukas Fleischer, our valued aur web maintainer. I suggest you create a feature request for AUR git over https support at https://bugs.archlinux.org/index.php?project=2 . There is already support for Git over https. It's read only though. The OP wants SSH git access on port 443. Which is something different. I believe that something along the lines of github with oAuth tokens should be better than having SSH operating on port 443. That way those who can't access regular SSH can still contribute to AUR.
Cheers, Giancarlo Razzolini
1. Yes, I do have network access outside of my corporate environment. However, much (READ: all) of the project maintenance and code lives on and is performed on my corporate servers.
2. I currently maintain the ownCloud-beta-client package as part of my involvement with that group. This is done as part of my official duties in my corporate environment.
My organization is also looking to begin sharing several large projects within a few months. Without another form of access, this would be technically impossible.
-- Thomas Swartz
I had been wondering if you were working on some packages in a work capacity. Given that, I think it would be a shame to lock out this type of contributor, even though there are probably just a few. As a network admin, I can say that blocking outbound SSH is pretty common. Yes, it is stupid, and it doesn't do much to improve the overall security of a corporate network. But it isn't really about security, it's about control. Corporate overlords are usually paranoid control freaks, and that often manifests in various policies, from HR policies to network and other IT policies and practices. And it sucks. It would be nice if the new AUR could find a way to allow the OPs continued participation.
On 18/06, David Kaylor wrote:
1. Yes, I do have network access outside of my corporate environment. However, much (READ: all) of the project maintenance and code lives on and is performed on my corporate servers.
2. I currently maintain the ownCloud-beta-client package as part of my involvement with that group. This is done as part of my official duties in my corporate environment.
My organization is also looking to begin sharing several large projects within a few months. Without another form of access, this would be technically impossible.
-- Thomas Swartz
I had been wondering if you were working on some packages in a work capacity. Given that, I think it would be a shame to lock out this type of contributor, even though there are probably just a few.
Since he's doing it as part of his job, supposedly, then I really can't see any reason at all that they wouldn't open up port 22 to just to luna for him. -- Sincerely, Johannes Löthberg PGP Key ID: 0x50FB9B273A9D0BB5 https://theos.kyriasis.com/~kyrias/
Since he's doing it as part of his job, supposedly, then I really can't see any reason at all that they wouldn't open up port 22 to just to luna for him.
Yea, who knows. Like I said earlier, I do feel for the guy.
participants (6)
-
David Kaylor
-
Giancarlo Razzolini
-
Johannes Löthberg
-
LoneVVolf
-
Martti Kühne
-
Tom Swartz