Welcome, Guest. Please login or register.

Author Topic: A challenge..  (Read 3099 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline Zac67

  • Hero Member
  • *****
  • Join Date: Nov 2004
  • Posts: 2890
    • Show all replies
Re: A challenge..
« on: March 26, 2011, 10:18:50 AM »
Exactly where is the challenge in that?
 

Offline Zac67

  • Hero Member
  • *****
  • Join Date: Nov 2004
  • Posts: 2890
    • Show all replies
Re: A challenge..
« Reply #1 on: March 26, 2011, 04:44:42 PM »
He should be looking out for a new job...

As long as HTTP connections are not completely blocked or 'whitelist only' you can certainly circumvent ANYTHING. Those irongates are smart but not omniscient.

You could obfuscate the real URL you're querying into some wild session-id like number and put the response into, say a GIF image. Locally (behind the irongate) you'd run a rather simple proxy that obfuscates the URLs and extracts the responses from the GIFs. At home you'd have a proxy doing exactly the opposite. All the irongate would be seeing is you retrieving GIF images from some server.

If the irongate allows for HTTPS then everything is VERY simple: set up a standard HTTP proxy with an SSL listening port and connect to that. Done.
 

Offline Zac67

  • Hero Member
  • *****
  • Join Date: Nov 2004
  • Posts: 2890
    • Show all replies
Re: A challenge..
« Reply #2 on: March 27, 2011, 04:54:05 PM »
No problem - just change the internal proxy (your tunneling proxy) to use the IG proxy for connecting out. It'll haul the data without knowing what it's about.