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.
On 20/06, Johannes Löthberg wrote:
I'm rather sure that he never actually said that maintaining the AUR
package was part of his job, just avoided the question by saying that
he worked on the software. (Though I'm too lazy to check now.)
Ah, seems I misread him, quoting
On Sat, Jun 20, 2015 at 09:12:06AM +0300, Mihamina Rakotomandimby wrote:
On 06/16/2015 09:24 AM, Alan Jenkins wrote:
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
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
On 20/06, David Kaylor wrote:
Do you have permission from your employer to user their infrastructure (eg:
computers, network) to work on contributions to ArchLinux?
If not, they *may* own the IP related to the PKGBUILDs, or any extra
scripts
you include (in most jurisdictions, if you write a
I'm rather sure that he never actually said that maintaining the AUR
package was part of his job, just avoided the question by saying that he
worked on the software. (Though I'm too lazy to check now.)
I just double checked, and this is what he wrote:
2. I currently maintain the
On 06/16/2015 09:24 AM, Alan Jenkins wrote:
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
Do you have permission from your employer to user their infrastructure (eg:
computers, network) to work on contributions to ArchLinux?
If not, they *may* own the IP related to the PKGBUILDs, or any extra
scripts
you include (in most jurisdictions, if you write a 15 line script, it's
On 2015-06-15 11:57, Tom Swartz wrote:
Hi all,
The majority of my work happens behind corporate firewalls where ssh out
via port 22 is not an option.
Is there a way to configure GitHub-like SSH via HTTPS ports?
https://help.github.com/articles/using-ssh-over-the-https-port/
I'd be
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
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
I'm not requiring that others solve my problem, Giancarlo.
As mentioned, this is an impossibility in our organization, and (I'm sure)
many others.
...or even hotels.
Damian.
Em 17-06-2015 22:24, Damian Nowak escreveu:
...or even hotels.
Ok. I can provide nginx, openssh and sshlp configuration to the AUR
maintainers if that's what you guys want. I bet that they already know
how to implement this anyway. But I still believe it's a dumb idea. Much
better to
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
Giancarlo,
This is stupid, as I already pointed.
The amount of neckbearding arguments you have posted here are not
productive.
Despite how 'stupid' the decisions are, either in your opinion or in fact,
repeatedly pointing it out has no bearing on the fact that it exists.
I'm complaining with
On Wed, Jun 17, 2015 at 2:17 PM, Tom Swartz t...@tswartz.net wrote:
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
On 06/16/2015 08:24 AM, Alan Jenkins wrote:
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
Actually they very often strip https traffic too. I used to work for
Symantec.cloud and we did both http and https scanning so don't try to say
that it is not a valid argument as I assure you you can scan and do content
filtering on https.
On 16 June 2015 at 14:35, Manuel Reimer
Em 16-06-2015 14:20, Alan Jenkins escreveu:
Also may I remind you that the focus of this conversation is allowing users
in corporate environments access to be able to contribute to the AUR. These
environments block SSH for multiple reasons but are able to allow HTTPS as
they are able to more
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
Hey Giancario,
Most of the large companies block everything and start from there, normally
everything is blocked outbound and only things that are business critical
are allowed until the business is able to function. In many cases they will
block all outbound traffic and only allow access to the
Em 16-06-2015 17:22, Alan Jenkins escreveu:
Most of the large companies block everything and start from there,
normally everything is blocked outbound and only things that are
business critical are allowed until the business is able to function.
In many cases they will block all outbound
On Tue, Jun 16, 2015 at 08:11:59PM -0300, Giancarlo Razzolini wrote:
Em 16-06-2015 17:22, Alan Jenkins escreveu:
[...]
The problem is that no matter how hard you moan at the people in
control of the firewalls they will normally not allow access to
something unless *they* deem it to be secure,
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
On 15 June 2015 at 21:33, Giancarlo Razzolini grazzol...@gmail.com wrote:
Em 15-06-2015 16:26, Tom Swartz escreveu:
With all due respect, requiring that a user punch holes in their security
firewalls is not a proper or long term solution to the issue at hand.
It is the only solution.
AFAICS
On Mon, 15 Jun 2015 11:57:26 -0400
Tom Swartz t...@tswartz.net wrote:
Hi all,
The majority of my work happens behind corporate firewalls where ssh out
via port 22 is not an option.
Is there a way to configure GitHub-like SSH via HTTPS ports?
Le mardi 16 juin 2015 01:37:36 Doug Newgard a écrit :
What it comes down to is that you want Arch to provide a way for you to
bypass security restrictions your employer has put into place. Does this
really sound like a good idea?
But Arch should be more committed and friendly to its
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
* Alexander Görtz a...@nyloc.de (Tue, 16 Jun 2015 11:04:51 +0200):
I think that this is a reason more to implement an alternative of
uploading a aur ball, as discussed in another thread, and creating a
git commit from it. I don't know any implementation details, but this
shouldn't be too hard
On 15/06, Tom Swartz wrote:
Hi all,
The majority of my work happens behind corporate firewalls where ssh out
via port 22 is not an option.
Is there a way to configure GitHub-like SSH via HTTPS ports?
https://help.github.com/articles/using-ssh-over-the-https-port/
I'd be greatly appreciative
Hi all,
The majority of my work happens behind corporate firewalls where ssh out
via port 22 is not an option.
Is there a way to configure GitHub-like SSH via HTTPS ports?
https://help.github.com/articles/using-ssh-over-the-https-port/
I'd be greatly appreciative if this was the case.
Thanks!
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
Em 15-06-2015 22:20, Tom Swartz escreveu:
I'm not requiring that others solve my problem, Giancarlo.
As mentioned, this is an impossibility in our organization, and (I'm sure)
many others.
Not that many, I hope.
There are many technical reasons for this limitation in our organization,
too
Instead of requiring others to solve your problem, you should explain to
your network administrators that this rule is counterproductive. I don't
really think that this will hinder adoption since port 22 is the default
ssh port.
I'm not requiring that others solve my problem, Giancarlo.
As
Em 15-06-2015 16:26, Tom Swartz escreveu:
With all due respect, requiring that a user punch holes in their security
firewalls is not a proper or long term solution to the issue at hand.
It is the only solution.
For home users, this might be a valid (although no less sane) solution, but
in
2015-06-15 16:33 GMT-03:00 Giancarlo Razzolini grazzol...@gmail.com:
Em 15-06-2015 16:26, Tom Swartz escreveu:
With all due respect, requiring that a user punch holes in their security
firewalls is not a proper or long term solution to the issue at hand.
It is the only solution.
Is not
Le 15/06/2015 22:00, Pablo Lezaeta Reyes a écrit :
2015-06-15 16:33 GMT-03:00 Giancarlo Razzolini grazzol...@gmail.com:
Em 15-06-2015 16:26, Tom Swartz escreveu:
A rule that denies outgoing SSH access is a dumb one. It doesn't protect
the rest of the devices on the network.
In my school
If your network admins don't know the difference between incoming and
outgoing ports, or not opening things like ssh ports to the internet that
really isn't an Arch problem...
- Justin
--
Regards,
Justin Dray
E: jus...@dray.be
M: 0433348284
Em 15-06-2015 17:00, Pablo Lezaeta Reyes escreveu:
Is not the only as pointer in this thread,
also you not considered the idea that burocracy for somethink that
simple as oppen a port could take months if not year or even coutless
failed attempts?
Well, each organization has it's own
39 matches
Mail list logo
