Hello,
I need to use a socks server to connect with a program but I don't
want to use any proxy server and just make my local computer "use" the
socks protocol so I'll need to enter e.g. 127.0.0.1:application port
in my program and the "socks program" will forward the request.

Thanks.

---

Request for Question Clarification by maniac-ga on 16 Feb 2005 19:19 PST

Can you please explain which operating system (and version) is on your
"local computer"?

The solution for something like Linux is likely much different than
for Microsoft Windows.

---

Clarification of Question by 3m1n3m-ga on 17 Feb 2005 02:27 PST

Maniac,

Windows XP Professional SP2

Thanks

---

Request for Question Clarification by rolnick-ga on 28 Feb 2005 17:02 PST

Please, clarify what program needs to connect via socks server, so we
can find adequate solution for you.

---

Clarification of Question by 3m1n3m-ga on 28 Feb 2005 17:44 PST

rolnick-ga,
I want ICQ 99b to connect through HTTP proxy but it only supports a socks

Hello, if I understand your question all you need is a port
forwarding, for that you can use Portmapper from AnalogX
http://www.analogx.com/contents/download/network/pmapper.htm
With this program you can easily setup which port forward to one or other ip.

Okay:

1. Get Antinat: http://antinat.sourceforge.net/.  This is my socks
server, and I do include a Win32 port with a decent installer.  Should
be up and running quickly.

2. Set your app to go to 127.0.0.1:1080.

(you're now going via socks.)

Okay: so you now want to connect your SOCKS proxy to an HTTP proxy? 
Go to http://antinat.sourceforge.net/doc/antinat.xml.4.shtml - and
look at the chaining section.  This describes how to upstream chain
your socks server to some other server, including HTTPS.

So this code should work:

<chain name='foobar'>
  <uri value='https://my.company.com:8080'/>
  <user value='myusername'/>
  <password value='mypassword'/>
</chain>

Then, in the filter section:

<filter source_addrtype='ipv4'>
<filter source_addr='127.0.0.1/32'>
<chain name='foobar'/>
</filter>
</filter>

More information needed to go beyond this:
Does the HTTPs proxy you want to connect through require
authentication? If not, remove the <user/> and <password/> lines.
Does the ICQ app support SOCKS authentication? If so, you can also
remove those lines; antinat will pass the authentication through to
your https proxy.
Does the https proxy require digest or windows authentication? If so,
antinat can't talk to it, sorry :(

- M

Hello malxau,
thanks alot for this answere!
where do I need to write the

<chain name='foobar'>
  <uri value='https://my.company.com:8080'/>
  <user value='myusername'/>
  <password value='mypassword'/>
</chain>

part?

icq will need to connect to login.icq.com:5190 or login.icq.com:443

Thank you!

ICQ will instruct the SOCKS server where it wants to connect.

The think I don't get with your question is that if your SOCKS server
is running locally, and doesn't connect to anything upstream, then
ICQ->SOCKS Server->Remote Server won't be any different to ICQ->Remote
Server.

I'm presuming then that the issue you have is you need to connect via
your company proxy, and it doesn't support SOCKS, hence the chain
command.

The chain section you quoted belongs at the top of antinat.xml;
outside of the filter and authchoice sections.  Put it directly after
the demonstration user account section.  Depending on which you chose
at setup, the files will be slightly different, so I can't be really
specific about where it belongs; but anywhere outside of filter and
authconfig should work.

Hello,
the problem is the following...ICQ99b is using the old ICQ protocol
which current servers doesnt support...anyhow they support the HTTP
protocol, no I want to connect as ICQ->local socks server->ICQ Server
via HTTP protocol.

Any way? :)

Again, I'm not seeing how the SOCKS server helps you any.

If there's an ICQ server that supports ICQ over HTTP, and your ICQ
client supports ICQ over HTTP, the two can talk just fine already -
SOCKS not required.

Some IM systems, including MSN, allow the HTTP method to help navigate
firewalls in tricky environments.  SOCKS does the same thing, but a
different way.

If you want to use an old ICQ client with a new ICQ server, what
you'll need is something that can bridge them - a 'router' that
supports both protocols.  SOCKS won't do that; it just passes the
network traffic from client to server and back.  If the two don't have
a protocol in common, it will fail, SOCKS or no SOCKS...

Hello,
ICQ 99b JUST supports socks server and no HTTP protocol thats why i
want to do icq->local socks->http to icq servers.

thanks

I think you're confusing two different meanings of "HTTP."

Instead, think "HTTP Server" and "HTTP Proxy."

A SOCKS Server is a type of proxy; it can connect to HTTP Servers, or
chain to HTTP Proxies, but it does not touch the data from the client
- the client talks to the remote server, via the SOCKS server.  No
data is manipulated on the way.

Can SOCKS connect to HTTP Servers (not proxies?) Sure.  But then, the
client app (in this case, ICQ) is talking HTTP to the HTTP Server.  So
if ICQ has no HTTP support, adding SOCKS in the middle doesn't
magically make ICQ HTTP compatible.

SOCKS *can* talk to an HTTP Proxy, and get that proxy to route the
request to another (3rd) server.  The HTTP Proxy is invisible to the
client (ICQ.)  But the 3rd server and ICQ still need to be able to
talk to each other; adding in SOCKS and an HTTP proxy can't make ICQ
magically change it's format to talk to HTTP Servers.

I think what you're asking for is just impossible without ICQ specific
software.  Is there any reason you can't upgrade your ICQ client?