How I learned about corporate firewalls
valcanbuild.tech
How I learned about corporate firewalls
1–10 of 204 posts
Re: How I learned about corporate firewalls
#2If I want to push to GitHub when I am in the office, I have to VPN out of the office connection because Port 22 is blocked.
And they wonder why I prefer to work from home?
Re: How I learned about corporate firewalls
#3If I want to push to GitHub when I am in the office, I have to VPN out of the office connection because Port 22 is blocked. And they wonder why I prefer to work from home?
Oh god this is horrible!
Yeah, I can't believe how stupidly locked down some of these networks are.
I once had an employer said they needed a "whitelist" of websites we wanted to visit instead of a "blacklist" of ones we shouldn't. That was an interesting day...
Re: How I learned about corporate firewalls
#4We once had to fight for stackoverflow access. Security responds: you devs should only require the manual provided by the vendor(in this case: Oracle javadocs)?
Re: How I learned about corporate firewalls
#5We once had to fight for stackoverflow access. Security responds: you devs should only require the manual provided by the vendor(in this case: Oracle javadocs)?
I would have taken that as my queue to start finding another job. Not that I can't puzzle everything out from scratch every single time I need to do anything, but why should I reinvent the wheel when off-the-shelf is both faster and higher quality?
Re: How I learned about corporate firewalls
#6If I want to push to GitHub when I am in the office, I have to VPN out of the office connection because Port 22 is blocked. And they wonder why I prefer to work from home?
Oh god this is horrible! Yeah, I can't believe how stupidly locked down some of these networks are. I once had an employer said they needed a "whitelist" of websites we wanted to visit instead of a "blacklist" of ones we shouldn't. That was an interesting day...
I had exactly this.
We run a Saas and someone wrote an email saying that our server was down, and when we'd expect it to be up. Not having had a notification, I double checked from a couple of geographic locations that our application was indeed up and responding.
After a bit of investigation, it turns out that they have to whitelist every unique address with their corporate IT. And had only whitelisted our primary client-app URL (talks to a couple of different API endpoints), hence the strange error message.
It's been a long time since I've worked somewhere with whitelisting.
Re: How I learned about corporate firewalls
#7We once had to fight for stackoverflow access. Security responds: you devs should only require the manual provided by the vendor(in this case: Oracle javadocs)?
About 2003/2004 I was working onsite at a customer that blocked access to Google - that was fun.
Re: How I learned about corporate firewalls
#8I'm currently in my very first job where running a local silent NTLM proxy is not a vital skill of survival. For similar reasons I somehow always made an opensource sonatype nexus that is doing pypy proxy or similar, so that operators team can actually do meaningful work without triggering security teams daily.
Re: How I learned about corporate firewalls
#9No post body was provided.
Re: How I learned about corporate firewalls
#10We once had to fight for stackoverflow access. Security responds: you devs should only require the manual provided by the vendor(in this case: Oracle javadocs)?
RE: RE: stackoverflow access
CC: Management
With such a strategy for learning everyone would end up in IT security.
Regards,
hyperman1