In message <_A3962@delegate-en.ML_> on 04/24/08(17:33:50) I wrote:
|I should have said that the encryption of configuration parameters by
|"-Fcredhy" (introduced at DeleGate/9.0.1 ) was a very tentative one without
|ability of verification of integirity of the decripted data (with CRC or
|MD5 or so). Thus it generates broken data if a given key for decryption
|is not equal to the one at the encryption, as shown in your case.
|I added another way of encryption at DeleGate/9.4.0 by "-Fenc" which is
|simpler (without password repository) and safer (with integirty check).
I'm reminded yet another way to encrypt parameters, to be implanted into
the executable file of DeleGate. In DeleGate/9.4.0, I introduced "-Fimp"
function to implant parameters of DeleGate directly into the executable
file of DeleGate, with encryption if necessary.
It can be used as follows:
0) see the usage
> dg.exe -Fimp -h
1) implanting parameters (into dg.exe itself in this case)
> dg.exe -Fimp ADMIN=foo@bar MYAUTH=user:pass
2) encrypting implanted parameters
> dg.exe -Fimp -k
> dg.exe -P9999
this is equivalent to:
> dg.exe -P9999 ADMIN=foo@bar MYAUTH=user:pass
See <URL:http://www.delegate.org/delegate/implant/> for more details.
And I noticed that this feature has been disabled for Win32 after
version DeleGate/9.8.1 since I changed the VC++ to VisualStudio 2005.
I fixed the problem in 9.8.2-pre27 which is currently available at
9 9 Yutaka Sato <email@example.com> 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