It worked ^^
I don't know what I was doing wrong.. I tried all kinds of things but I
don't think I ever tried specifically putting "delegate" in the connect
I then tried using a method like you suggested in
because I need all the communication to be encrypted.
I now have
dg8_3_3.exe -f -v SERVER=tcprelay://masteraddr:8080 SSLTUNNEL=proxyaddr:8080
I guess this is encrypting the raw data over the tcprelay and decrypting at
the other end where the delegate server sees the data as the proxy server
attempting a connection directly.
This seems to work fine, and presumably I can set the delegate at the other
end to proxy whatever I need.
Only problem seems to be that every connection from my applications opens a
new connection through the proxy, with ssl negotiation every time. This
doesn't really matter I suppose, but I just wonder why the delegate->master
delegate connection with sslway doesn't encrypt the first connection text?
Anyway.. What I have now is much better than what I was using before which
was one delegate as the proxy on my master machine, one on my client machine
to connect through the local proxy and a ssh to encrypt the data.. ^^;
Yutaka Sato writes:
> In message <_A2110@delegate-en.ML_> on 02/06/03(11:31:03)
> you email@example.com wrote:
> |How can I make one delegate connect to another via a proxy?
> |Whenever I try, it always tries to connect directly to master server and
> |doesn't try the proxy..
> How did you do it?
> Connection to a MASTER-DeleGate (dgHost:dgPort) via SSLTUNNEL by a HTTP-proxy
> (pxHost:pxPort) can be specified like this:
> MASTER=dgHost:dgPort SSLTUNNEL=pxHost:pxPort CONNECT=https:delegate
> @ @ Yutaka Sato <firstname.lastname@example.org> http://www.delegate.org/y.sato/
> ( - ) National Institute of Advanced Industrial Science and Technology (AIST)
> _< >_ 1-1-4 Umezono, Tsukuba, Ibaraki, 305-8568 Japan
> Do the more with the less -- B. Fuller