Liz Quilty wrote: > Surely if work has blocked it then you shouldnt be using it. In an ideal world companies would have efficient firewall processes which would quickly evaluate a request to modify a firewall rule, and to quickly implement a change. Most companies however either have nobody responsible for the firewall - it is simply an appliance, often one that is in the ADSL router itself, or in larger organisations it is controlled by a administrator whose sole purpose in life is "ensuring security"; thus any change to the most limited configuration is a security threat. The consequence is that the average developer hasn't a hope in hell of changing a organisations firewall rules, while needing vital resources outside the organisation to complete a project. Being right about a companies poor resourcing in the security/firewall area is cold comfort when you are living on the street after bing kicked out of the flat when you were fired for not completing that project on time. Okay, perhaps I'm exaggerating a little, but the point is that often developers do whats needed to get the job done, and most of the time there is no question about the means. However, once or twice in the states employees have been taken to task about "evading company security measures". Hard places and rocks come to mind....
| More information about the AuckLUG mailing list |
If you have any questions or comments about this page, email the
Webmaster Design Copyright © 1998-2005 Linux.net.nz |