Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

I work at a huge corporate with a huge corporate firewall that blocks most outgoing services other than http and https. But my team needs access to a tame LAMP server to help them do their jobs.

I'm no expert, but would we be able to achieve this by setting up an EC2 instance with services listening on non-standard ports? I think we'd mainly need ssh, smb and rsync, so I'm thinking (for example) one IP for Apache on port 80, another for ssh on port 80 and smb on 443, and another for rsync on port 80. I think these would all be TCP but I'm not sure.

The team can then just connect to those addresses on those ports and "tunnel" out of the LAN.

Or am I smoking crack?

share|improve this question

migrated from meta.serverfault.com Jun 10 '11 at 20:45

This question came from our discussion, support, and feature requests site for system and network administrators.

closed as off topic by Zypher Jun 10 '11 at 20:50

Questions on Server Fault are expected to relate to server, networking, or related infrastructure administration within the scope defined by the community. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Read more about reopening questions here.If this question can be reworded to fit the rules in the help center, please edit the question.

2  
Just an FYI, not a good idea to ask a bunch of system administrators how to bypass your local sysadmins security. –  ErnieTheGeek Jun 10 '11 at 21:08
1  
Have you considered, I don't know, running this up the chain of command? If you really need access to it to do your jobs, then it can be made available without backdooring it. –  Holocryptic Jun 10 '11 at 21:22
    
All things considered, I think that last sentence would be my first choice. –  John Gardeniers Jun 10 '11 at 23:36

2 Answers 2

up vote 1 down vote accepted

Unlikely. Big corporate firewalls are smart enough to notice that traffic passing over TCP/80 is patently not HTTP-like and block it. There are ways to tunnel ssh over HTTPS, but that's why BCF's tend to restrict SSL-enabled sites as well, especially if they're worried about the corporate Intellectual Property leaving via unauthorized routes such as SSL-encrypted Gmail.

Your most reliable way is to try and work with your IT department to figure out a workable solution. Everything else may end up in disciplinary procedures for circumventing network security procedures.

share|improve this answer
    
Thanks - I thought as much. –  Gilgongo Jun 10 '11 at 21:10

If it is a "tame" server and your team needs it to do their job, contact your IT department and have them allow access.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.