In message <_A3553@delegate-en.ML_> on 10/19/06(22:00:23)
you email@example.com wrote:
|is it possible to have myauth=user:pass in the same manner as -Fauth
|dgauth ( aka encrypted data in a file ) because
|on a command line invokement the myauth is shown in clear text .
You can encrypt your configuration parameters including MYAUTH stored
in a parameter file, like +="config.cdh", as described in
I also thought about the encryption of MYAUTH as you say, crypting it
as the MD5 password in AUTHORIZER, but I thought it should be covered
with the above generic encryption of parameters.
For example, MYAUTH=user:pass:socks MYAUTH=user:pass:http-proxy and
MYAUTH=user:pass:delegate will be able to be represented as
in the future release, and whatever extended parameters will be crypted
with the single scheme of the encryption of a configuration file.
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