In message <_A3546@delegate-en.ML_> on 10/18/06(18:36:53)
you email@example.com wrote:
|i recently discovered a security flaw which is related to the delegate
|allthough using a filter like FCL="sslway ..... -Vrfy" , when running in
|master mode , clients which are rejected by the ssl-layer, still
|cause delegate to open a connection to a destination server , this can and
|has been used to accomplish ddos . the FCL should reject the connection
|establishment to an arbitrary server , before rejecting the ssl handshake
|. in case you need log files for forensik analysis, i will post them. for
|now, i strongly
|recommend everyone to shut down delegate master services until this one is
Maybe you are using a version of DeleGate older than DeleGate/9.2.5-pre7.
As written in <URL:http://www.delegate.org/delegate/tls/> after DeleGate/9.0
I'm shifting to STLS=fcl,fsv instead obsoleted FCL,FSV=sslway in the recent
versions. In fact, FCL,FSV=sslway for MASTER is disabled in 9.2.5-pre7.
With STLS=fcl, the whole communication between DeleGates is encrypted with
SSL, so if the SSL-layer is not established, no father action will be taken.
Chaining DeleGates with MASTER and STLS can be done as follows.
a% delegated -Pa:8888 STLS=fcl
b% delegated -Pb:8023 STLS=fsv MASTER=a:8888 SERVER=telnet
You can use authentication by client-side certificate as follows:
a% delegated -Pa:8888 STLS="fcl,sslway -Vrfy"
b% delegated -Pb:8023 STLS="fsv,sslway -cert file" MASTER=a:8888 SERVER=telnet
Now the latest pre-release version of DeleGate has become 9.2.5-pre19 which
is almost ready to be released as an official version DeleGate/9.2.5
to be released tomorrow <URL:http://delegate.org/mail-lists/delegate/13534>
So you are strongly recommended to use the latest version of DeleGate with
9 9 Yutaka Sato <firstname.lastname@example.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