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
>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
>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 men
Thanks for the replies.
> The OP should use a proxy, VPN, or other methods to punch a hole through
the corporate firewall for being able to access the aur host.
Unfortunately, this is not an option by any means.
With all due respect, requiring that a user punch holes in their security
firewalls
hanks!
--
Tom Swartz
