legacyb4 said:
You still need a way for public (Internet) traffic to reach your Mac sitting behind the corporate firewall.
I would actually do the smart thing and make a case for getting secure access to your Mac through VPN rather than putting yourself at risk for deliberately crossing company policy. If outbound HTTP is the only protocol allowed, your company must have good reason to be so strict.
My $0.02.
My Mac is sitting at home. I'm trying to access it from work. I can access my home PCs from work. The corporate policy here is not strict, rather the implementation is sweeping prob. for admin reasons, because the company is so enormous and they can't manage making allowances for people so they just apply a blanket policy to all. I'm not sure they'd understand how to do it anyway, as it took them four weeks to create a Windows domain account for me. Anyway, I'd rather focus on the solution of getting access over http, as this is the only way it's going to work. The solution on the PC was simple (
http://www.gotomypc.com), and I want a simple solution for the Mac.
You should have a look at how GoToMyPc works, it's quite clever. In a nutshell, the host machine does not listen for requests, rather it initiates a connection to the GoToMyPc servers and maintains a heartbeat. On every heartbeat it checks to see if a connection is "incoming" and then it connects to the remote machine. This way, all connections are outgoing over http, which means that firewall configuration is completely redundant because 99.9% of firewalls allow outbound http traffic. I want this kind of set up for the Mac.
Anyone?
)