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

[DeleGate-En] password auth. of SockMux (Re: SSL between SOCKS-DeleGate)
03 Aug 2006 17:45:11 GMT (Yutaka Sato)
The DeleGate Project


In message <_A3441@delegate-en.ML_> on 08/03/06(10:55:49) I wrote:
 |You can use SSL-certificate for MASTER ans SockMux too if you connect
 |between DeleGate with SSLway.
 |You can use AUTHORIZER and MYAUTH for the chaining of DeleGate by MASTER
 |as this for example:
 | % delegated -P8888 FCL=sslway SERVER=delegate AUTHORIZER="-list{user:pass}"
 | % delegated -P8080 FSV=sslway SERVER=http MASTER=host:8888 MYAUTH=user:pass
 |You can use CRYPT=pass:password to disable communication with those
 |who don't know the password as this:
 | % delegated -P8000 FCL=sslway CRYPT=pass:xxxx SERVER=sockmux ...
 | % delegated -P9000 FSV=sslway CRYPT=pass:xxxx SERVER=sockmux://host:8000 ...

I uploaded 9.2.4-pre11 which introduced password authentication for SockMux.
Now you can use AUTHORIZER + MYAUTH with SERVER=sockmux as this:

 % delegated -P8000 SERVER=sockmux             AUTHORIZER="-list{uc:pc}" ...
 % delegated -P9000 SERVER=sockmux://host:8000 MYAUTH=uc:pc ...

The authentication is bidirectional, that is, both the server and the client
may ask password authentication to the peer as this: 

 % delegated -P8000 SERVER=sockmux             AUTHORIZER="-list{uc:pc}" MYAUTH=us:ps ...
 % delegated -P9000 SERVER=sockmux://host:8000 AUTHORIZER="-list{us:ps}" MYAUTH=uc:pc ...

  9 9   Yutaka 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]