Article delegate-en/4269 of [1-5169] on the server localhost:119
  upper oldest olders older1 this newer1 newers latest
search
[Top/Up] [oldest] - [Older+chunk] - [Newer+chunk] - [newest + Check]
[Reference:<_A4267@delegate-en.ML_>]
Newsgroups: mail-lists.delegate-en

[DeleGate-En] Re: SOCKMUX
16 Dec 2008 08:32:22 GMT feedback@delegate.org (Yutaka Sato)
The DeleGate Project


Hi,

In message <_A4267@delegate-en.ML_> on 12/16/08(02:36:50)
you Deborah Charan <puyiabdyi-bfkmicdyir3r.ml@ml.delegate.org> wrote:
 |Just to confirm that I could get the socks portion to work, the 
 |following works fine:
 |
 |host A --> sockd
 |host B --> ./delegated SERVER=socks -P8010 SOCKS=hostA:1080
 |
 |Then I try and get a tunnel between A and B having host Y send data to 
 |host X using Socks over the SOCKMUX  tunnel.
 |
 |host A --> ./delegated SOCKMUX=hostA:8000:acc SERVER=socks -P1080
 |host B --> ./delegated SOCKMUX=hostA:8000:con SERVER=socks -P8010 
 |SOCKS=hostA:1080

If you saw a message like 'Forbidden xx.xx.xx.xx:xxxx' in your log of
DeleGate (xx.xx.xx.xx is the IP-address of hostB), the failure is
due to the default access control.
The access control for automatic SockMux for SOCKS had been too strict
since 9.2.4 till 9.8.5.  It can be used only in "localhost".  That is,
you will succeed only if your hostA and hostB is the same "localhost".
It can be called a bug because I did not intend such strict restriction
at that time.
I deregulated it in 9.8.6, and fixed many other bugs and latency in
SockMux, then introduced CAPSKEY to restrict the abuses of it.

Cheers,
Yutaka
--
  9 9   Yutaka Sato <y.sato@delegate.org> http://delegate.org/y.sato/
 ( ~ )  National Institute of Advanced Industrial Science and Technology
_<   >_ 1-1-4 Umezono, Tsukuba, Ibaraki, 305-8568 Japan
Do the more with the less -- B. Fuller

  admin search upper oldest olders older1 this newer1 newers latest
[Top/Up] [oldest] - [Older+chunk] - [Newer+chunk] - [newest + Check]
@_@V